Tools & Wizards About Us
john.do screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

john.do

Page Load Speed

951 ms in total

First Response

16 ms

Resources Loaded

223 ms

Page Rendered

712 ms

john.do screenshot

About Website

Click here to check amazing John content for Pakistan. Otherwise, check out these important facts you probably never knew about john.do

Hacker. Human.

Visit john.do

Key Findings

We analyzed John.do page load time and found that the first response time was 16 ms and then it took 935 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

john.do performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

john.do

16 ms

css

29 ms

8b787e597e7d457d52e9b4d23c23a6ab.css

11 ms

672e8e307bcd816f00970635d83688a3.css

14 ms

4d44a295bdc261c9f5247976edf2afea.css

20 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 73% of them (19 requests) were addressed to the original John.do, 4% (1 request) were made to Fonts.googleapis.com and 4% (1 request) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (125 ms) relates to the external source 2.gravatar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.8 kB (7%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of John.do main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.4 kB

  • Original 46.4 kB
  • After minification 46.2 kB
  • After compression 10.0 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 36.4 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 66.7 kB

  • Original 1.9 MB
  • After minification 1.8 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. John images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 32.0 kB

  • Original 58.6 kB
  • After minification 58.6 kB
  • After compression 26.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 55% of the original size.

CSS Optimization

-75%

Potential reduce by 1.8 kB

  • Original 2.3 kB
  • After minification 2.1 kB
  • After compression 578 B

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. John.do needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (48%)

Requests Now

23

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

john.do

john.do

16 ms

css

css

29 ms

8b787e597e7d457d52e9b4d23c23a6ab.css

8b787e597e7d457d52e9b4d23c23a6ab.css

11 ms

672e8e307bcd816f00970635d83688a3.css

672e8e307bcd816f00970635d83688a3.css

14 ms

4d44a295bdc261c9f5247976edf2afea.css

4d44a295bdc261c9f5247976edf2afea.css

20 ms

09f8dfa4dd076e5c51815d0613cd834c.js

09f8dfa4dd076e5c51815d0613cd834c.js

26 ms

d388a1994c7a37fcc7318ae204afacf2.js

d388a1994c7a37fcc7318ae204afacf2.js

9 ms

devicepx-jetpack.js

devicepx-jetpack.js

68 ms

e-201609.js

e-201609.js

5 ms

ab3c2aecd3dca0cc0aca3694bcf73158.js

ab3c2aecd3dca0cc0aca3694bcf73158.js

24 ms

bf7bebaaad7666c747f28ccdc8cde089.js

bf7bebaaad7666c747f28ccdc8cde089.js

25 ms

43fd06913bac1fc96955b29d7b415056.js

43fd06913bac1fc96955b29d7b415056.js

23 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

60 ms

analytics.js

analytics.js

124 ms

2801f5145de98010dd72f1ac6d92938f

2801f5145de98010dd72f1ac6d92938f

125 ms

book-1200x532.jpg

book-1200x532.jpg

116 ms

weave-in-1-1200x747.png

weave-in-1-1200x747.png

119 ms

roenne-arden.jpg

roenne-arden.jpg

115 ms

ruler-pencil-eraser-sharpener-1200x800.jpg

ruler-pencil-eraser-sharpener-1200x800.jpg

113 ms

1-qPkeL121gXx5oE74a3Zufg.png

1-qPkeL121gXx5oE74a3Zufg.png

117 ms

stairway-hands.jpg

stairway-hands.jpg

116 ms

31grant-superJumbo-1200x813.jpg

31grant-superJumbo-1200x813.jpg

117 ms

tomo-transparent.png

tomo-transparent.png

115 ms

Genericons.svg

Genericons.svg

70 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

69 ms

g.gif

g.gif

68 ms

Accessibility Review

john.do accessibility score

62

Accessibility Issues

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-*] attributes do not match their roles

High

ARIA progressbar elements do not have accessible names.

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

john.do 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

john.do SEO score

92

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

High

Tap targets are not sized appropriately

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 John.do 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 John.do 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

john.do

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