Tools & Wizards About Us
imeidoctor.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

imeidoctor.com

Free Phone IMEI Check and Unlocking - IMEIdoctor.com

Page Load Speed

9.2 sec in total

First Response

272 ms

Resources Loaded

7.4 sec

Page Rendered

1.5 sec

imeidoctor.com screenshot

About Website

Click here to check amazing IMEIdoctor content for Turkey. Otherwise, check out these important facts you probably never knew about imeidoctor.com

Free Phone IMEI unlocking services and Phone IMEI checker with Carrier information, SIM Lock status, Find My iPhone (iCloud Activation Lock) status

Visit imeidoctor.com

Key Findings

We analyzed Imeidoctor.com page load time and found that the first response time was 272 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

imeidoctor.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

imeidoctor.com

272 ms

en_au

738 ms

7c99dff69f.js

106 ms

css

58 ms

hs.megamenu.css

212 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 53% of them (59 requests) were addressed to the original Imeidoctor.com, 24% (27 requests) were made to Directunlocks.com and 4% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Imeidoctor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.3 kB (3%)

Content Size

13.6 MB

After Optimization

13.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imeidoctor.com main page is 13.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 13.2 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 310.6 kB

  • Original 336.8 kB
  • After minification 257.0 kB
  • After compression 26.2 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. This page needs HTML code to be minified as it can gain 79.8 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 310.6 kB or 92% of the original size.

Image Optimization

-1%

Potential reduce by 123.0 kB

  • Original 13.2 MB
  • After minification 13.0 MB

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. IMEIdoctor images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 67 B

  • Original 21.7 kB
  • After minification 21.7 kB
  • After compression 21.6 kB

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

-14%

Potential reduce by 13.6 kB

  • Original 94.3 kB
  • After minification 94.3 kB
  • After compression 80.7 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. Imeidoctor.com needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (40%)

Requests Now

109

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imeidoctor.com

imeidoctor.com

272 ms

en_au

en_au

738 ms

7c99dff69f.js

7c99dff69f.js

106 ms

css

css

58 ms

hs.megamenu.css

hs.megamenu.css

212 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

151 ms

custombox.min.css

custombox.min.css

248 ms

slick.css

slick.css

212 ms

jquery.fancybox.css

jquery.fancybox.css

225 ms

animate.min.css

animate.min.css

63 ms

frontend.css

frontend.css

176 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

56 ms

dataTables.bootstrap.min.css

dataTables.bootstrap.min.css

65 ms

email-decode.min.js

email-decode.min.js

160 ms

app.js

app.js

321 ms

slidebar.js

slidebar.js

301 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

29 ms

dataTables.bootstrap.min.js

dataTables.bootstrap.min.js

31 ms

lazyload.min.js

lazyload.min.js

82 ms

hs.megamenu.js

hs.megamenu.js

479 ms

jquery.validate.min.js

jquery.validate.min.js

460 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

486 ms

custombox.min.js

custombox.min.js

495 ms

custombox.legacy.min.js

custombox.legacy.min.js

671 ms

slick.js

slick.js

503 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

513 ms

hs.core.js

hs.core.js

501 ms

hs.header.js

hs.header.js

513 ms

hs.unfold.js

hs.unfold.js

526 ms

hs.validation.js

hs.validation.js

521 ms

hs.focus-state.js

hs.focus-state.js

597 ms

hs.malihu-scrollbar.js

hs.malihu-scrollbar.js

719 ms

hs.modal-window.js

hs.modal-window.js

606 ms

hs.show-animation.js

hs.show-animation.js

720 ms

hs.slick-carousel.js

hs.slick-carousel.js

721 ms

hs.fancybox.js

hs.fancybox.js

779 ms

hs.go-to.js

hs.go-to.js

719 ms

jquery.counterup.min.js

jquery.counterup.min.js

60 ms

js

js

137 ms

typer.js

typer.js

130 ms

selectize.min.js

selectize.min.js

73 ms

countUp.min.js

countUp.min.js

85 ms

ipad-colour.png

ipad-colour.png

247 ms

doctor.png

doctor.png

100 ms

apple-watch.png

apple-watch.png

446 ms

iphone-12-1.png

iphone-12-1.png

454 ms

iphone-4-1.png

iphone-4-1.png

1990 ms

iphone-x.png

iphone-x.png

442 ms

iphone-15.png

iphone-15.png

452 ms

iphone-14-normal.png

iphone-14-normal.png

454 ms

iphone-12-mini.png

iphone-12-mini.png

536 ms

iphone-7-1.png

iphone-7-1.png

540 ms

iphone-5c.png

iphone-5c.png

605 ms

iphone-12-normal.png

iphone-12-normal.png

662 ms

iphone-13.png

iphone-13.png

609 ms

iphone-13-mini.png

iphone-13-mini.png

665 ms

iphone14better.png

iphone14better.png

715 ms

iphone-11-pro.png

iphone-11-pro.png

1322 ms

iphone-13-standard.png

iphone-13-standard.png

706 ms

iphone-xr.png

iphone-xr.png

1415 ms

iphone-5-1.png

iphone-5-1.png

1418 ms

iphone-11-standard.png

iphone-11-standard.png

1412 ms

iphone-6-1.png

iphone-6-1.png

1418 ms

15-pro-max.png

15-pro-max.png

1414 ms

iphonese.png

iphonese.png

1525 ms

iphonese2020.png

iphonese2020.png

1526 ms

iphone-8-1.png

iphone-8-1.png

4133 ms

mac.png

mac.png

1500 ms

maetro.png

maetro.png

1523 ms

JCBcard.png

JCBcard.png

1608 ms

iconfinder_8_credit_2629973.svg

iconfinder_8_credit_2629973.svg

461 ms

iconfinder_4_credit_2629972.svg

iconfinder_4_credit_2629972.svg

468 ms

drlogo.png

drlogo.png

702 ms

usa.png

usa.png

1408 ms

argentina.png

argentina.png

1407 ms

australia.png

australia.png

1407 ms

austria.png

austria.png

1406 ms

bolivia.png

bolivia.png

1407 ms

brazil.png

brazil.png

1407 ms

canada.png

canada.png

1499 ms

chile.png

chile.png

1494 ms

colombia.png

colombia.png

1466 ms

egypt.png

egypt.png

1452 ms

css

css

45 ms

france.png

france.png

1451 ms

india.png

india.png

1448 ms

ireland.png

ireland.png

1542 ms

italy.png

italy.png

1439 ms

japan.png

japan.png

1380 ms

mexico.png

mexico.png

1536 ms

panama.png

panama.png

1282 ms

peru.png

peru.png

1275 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

21 ms

philippines.png

philippines.png

1267 ms

portugal.png

portugal.png

1341 ms

spain.png

spain.png

1363 ms

sweden.png

sweden.png

1406 ms

switzerland.png

switzerland.png

1341 ms

uk.png

uk.png

1432 ms

drlogo_white.png

drlogo_white.png

1421 ms

shutterstock_715081060.jpeg

shutterstock_715081060.jpeg

5748 ms

slick-carousel-preloader-primary.svg

slick-carousel-preloader-primary.svg

1404 ms

bg2.png

bg2.png

1451 ms

head-background-min.png

head-background-min.png

1399 ms

ribbit.min.js

ribbit.min.js

694 ms

js

js

72 ms

js

js

57 ms

analytics.js

analytics.js

25 ms

collect

collect

87 ms

collect

collect

37 ms

ga-audiences

ga-audiences

33 ms

Accessibility Review

imeidoctor.com accessibility score

76

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

imeidoctor.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

imeidoctor.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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 Imeidoctor.com 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 Imeidoctor.com 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

imeidoctor.com

Open Graph description is not detected on the main page of IMEIdoctor. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: