Tools & Wizards About Us
imeicheck.net screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

imeicheck.net

IMEI Check - Free Online IMEI & ESN Number Checker Service | IMEIcheck.net

Page Load Speed

1.5 sec in total

First Response

59 ms

Resources Loaded

787 ms

Page Rendered

658 ms

imeicheck.net screenshot

About Website

Visit imeicheck.net now to see the best up-to-date IMEI Check content and also check out these interesting facts you probably never knew about imeicheck.net

Check your IMEI / ESN for FREE. Check IMEI Number and find out hidden info. You will receive all info - hardware specification, warranty or BLACKLIST status and more. All devices supported

Visit imeicheck.net

Key Findings

We analyzed Imeicheck.net page load time and found that the first response time was 59 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

imeicheck.net performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

imeicheck.net

59 ms

imeicheck.net

94 ms

blacklist-status-check.CUShZxCd.css

12 ms

index.CTcCxSPF.css

28 ms

motorola.DT1IjEBS.css

21 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that all of those requests were addressed to Imeicheck.net and no external sources were called. The less responsive or slowest element that took the longest time to load (385 ms) belongs to the original domain Imeicheck.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.4 kB (44%)

Content Size

117.0 kB

After Optimization

65.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imeicheck.net main page is 117.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 64.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 51.1 kB

  • Original 64.4 kB
  • After minification 64.4 kB
  • After compression 13.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 40.4 kB
  • After minification 40.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. IMEI Check images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 363 B

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 11.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Imeicheck.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (26%)

Requests Now

50

After Optimization

37

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMEI Check. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

imeicheck.net

imeicheck.net

59 ms

imeicheck.net

imeicheck.net

94 ms

blacklist-status-check.CUShZxCd.css

blacklist-status-check.CUShZxCd.css

12 ms

index.CTcCxSPF.css

index.CTcCxSPF.css

28 ms

motorola.DT1IjEBS.css

motorola.DT1IjEBS.css

21 ms

index.D9-BYDBq.css

index.D9-BYDBq.css

45 ms

index.C2fKZhC1.css

index.C2fKZhC1.css

30 ms

email-decode.min.js

email-decode.min.js

14 ms

mobile-logo.C6ah2HpR_Zg65L1.svg

mobile-logo.C6ah2HpR_Zg65L1.svg

18 ms

logo.PkuYZ2g-_A4OX7.svg

logo.PkuYZ2g-_A4OX7.svg

17 ms

imeiStatic1.Cq9T91Q5.svg

imeiStatic1.Cq9T91Q5.svg

22 ms

imeiStatic2.BQNv2O_o.svg

imeiStatic2.BQNv2O_o.svg

20 ms

imeiStatic3.nc-dC0Xx.svg

imeiStatic3.nc-dC0Xx.svg

13 ms

firstBlock.Ba8c4csf_29wLya.svg

firstBlock.Ba8c4csf_29wLya.svg

27 ms

secondBlock.CB2zPEus_Z1CEm8u.svg

secondBlock.CB2zPEus_Z1CEm8u.svg

25 ms

thirdBlock.BsbSV9eX_XpYOM.svg

thirdBlock.BsbSV9eX_XpYOM.svg

29 ms

left-background.BpyWlqVP_2sj1Wr.svg

left-background.BpyWlqVP_2sj1Wr.svg

28 ms

right-background.huoXomjC_1mIk67.svg

right-background.huoXomjC_1mIk67.svg

36 ms

left-banner.F-GrndIT_j92TE.svg

left-banner.F-GrndIT_j92TE.svg

30 ms

right-banner.pJJXR21E_Zb9NP5.svg

right-banner.pJJXR21E_Zb9NP5.svg

40 ms

left.AbHLtBPd_Z6YojS.svg

left.AbHLtBPd_Z6YojS.svg

87 ms

right.DiMylRpm_megGF.svg

right.DiMylRpm_megGF.svg

37 ms

left-background.Cg0dPyio_Z2m4unJ.svg

left-background.Cg0dPyio_Z2m4unJ.svg

42 ms

right-background.BsAM9FP5_Z25um1n.svg

right-background.BsAM9FP5_Z25um1n.svg

50 ms

left-top.BWNSdvfK_19y1PV.svg

left-top.BWNSdvfK_19y1PV.svg

92 ms

right-top.BeVBoQsk_1toSe.svg

right-top.BeVBoQsk_1toSe.svg

88 ms

right-bottom.Bd3FyFLB_1VyFRB.svg

right-bottom.Bd3FyFLB_1VyFRB.svg

99 ms

left.syObObGS_AzFpx.svg

left.syObObGS_AzFpx.svg

102 ms

middle.DzcWk386_1uQjBW.svg

middle.DzcWk386_1uQjBW.svg

105 ms

right.5J60iOzy_Ef4ra.svg

right.5J60iOzy_Ef4ra.svg

139 ms

left.CKJ0_gmT_Z1oXxC0.svg

left.CKJ0_gmT_Z1oXxC0.svg

97 ms

middle.Dh-Kio3e_Z228oqG.svg

middle.Dh-Kio3e_Z228oqG.svg

111 ms

right.BXNgXuC6_ZWlvqf.svg

right.BXNgXuC6_ZWlvqf.svg

109 ms

AdamKonord2x.jpg

AdamKonord2x.jpg

116 ms

BobClarks2x.jpg

BobClarks2x.jpg

183 ms

AngelRobles2x.jpg

AngelRobles2x.jpg

126 ms

OliverCasey2x.jpg

OliverCasey2x.jpg

362 ms

SophieWalsh2x.jpg

SophieWalsh2x.jpg

241 ms

NataliaAlvarado2x.jpg

NataliaAlvarado2x.jpg

340 ms

JoshuaStevenson2x.jpg

JoshuaStevenson2x.jpg

358 ms

WilliamHampton2x.jpg

WilliamHampton2x.jpg

366 ms

JaniceMorgan2x.jpg

JaniceMorgan2x.jpg

368 ms

LoganBell2x.jpg

LoganBell2x.jpg

385 ms

visa-logo.DdZvN8cN_Z2qOHOV.svg

visa-logo.DdZvN8cN_Z2qOHOV.svg

342 ms

main.js

main.js

351 ms

mastercard.CFArQW4l_1AvdpV.svg

mastercard.CFArQW4l_1AvdpV.svg

357 ms

american-express-logo.CUqLlytD_Z1ydhOz.svg

american-express-logo.CUqLlytD_Z1ydhOz.svg

360 ms

stripe.-Wn2r_C4_Z1Qqzmg.svg

stripe.-Wn2r_C4_Z1Qqzmg.svg

358 ms

apple-pay.I4R_ijYL_Z2wpXVS.svg

apple-pay.I4R_ijYL_Z2wpXVS.svg

360 ms

google-pay.D7njmdt-_b4SjA.svg

google-pay.D7njmdt-_b4SjA.svg

361 ms

dmca-protected.RdJwyXPi_Z28jbgO.svg

dmca-protected.RdJwyXPi_Z28jbgO.svg

362 ms

gtm.js

gtm.js

161 ms

Accessibility Review

imeicheck.net accessibility score

97

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

imeicheck.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

imeicheck.net SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imeicheck.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Imeicheck.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

imeicheck.net

Open Graph data is detected on the main page of IMEI Check. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: