Tools & Wizards About Us
whoschecking.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whoschecking.com

Page Load Speed

4.2 sec in total

First Response

1.2 sec

Resources Loaded

2.8 sec

Page Rendered

272 ms

whoschecking.com screenshot

About Website

Welcome to whoschecking.com homepage info - get ready to check Whoschecking best content right away, or after learning these important things about whoschecking.com

Who's Checking?

Visit whoschecking.com

Key Findings

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

Performance Metrics

whoschecking.com performance score

0

Network Requests Diagram

whoschecking.com

1151 ms

responsive.css

263 ms

bootstrap.min.css

743 ms

font-awesome.min.css

347 ms

css

26 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 89% of them (31 requests) were addressed to the original Whoschecking.com, 9% (3 requests) were made to Fonts.googleapis.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Whoschecking.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 485.4 kB (24%)

Content Size

2.0 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whoschecking.com 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 12.6 kB

  • Original 17.0 kB
  • After minification 14.4 kB
  • After compression 4.4 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 2.6 kB, which is 15% 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 12.6 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 119.9 kB

  • Original 1.5 MB
  • After minification 1.4 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. Whoschecking images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 106.4 kB

  • Original 193.4 kB
  • After minification 191.6 kB
  • After compression 87.0 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 106.4 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 246.4 kB

  • Original 291.8 kB
  • After minification 260.9 kB
  • After compression 45.4 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. Whoschecking.com needs all CSS files to be minified and compressed as it can save up to 246.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (47%)

Requests Now

32

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoschecking.com

whoschecking.com

1151 ms

responsive.css

responsive.css

263 ms

bootstrap.min.css

bootstrap.min.css

743 ms

font-awesome.min.css

font-awesome.min.css

347 ms

css

css

26 ms

css

css

38 ms

hover-min.css

hover-min.css

502 ms

styles.css

styles.css

261 ms

css

css

43 ms

genericons.css

genericons.css

345 ms

style.css

style.css

515 ms

jquery.js

jquery.js

649 ms

jquery-migrate.min.js

jquery-migrate.min.js

415 ms

jquery.min.js

jquery.min.js

76 ms

bootstrap.min.js

bootstrap.min.js

469 ms

jquery.form.min.js

jquery.form.min.js

626 ms

scripts.js

scripts.js

557 ms

comment-reply.min.js

comment-reply.min.js

548 ms

bg.png

bg.png

875 ms

logo.png

logo.png

118 ms

icon2.png

icon2.png

107 ms

icon3.png

icon3.png

109 ms

sliderimg1.jpg

sliderimg1.jpg

302 ms

sliderimg2.jpg

sliderimg2.jpg

424 ms

sliderimg3.jpg

sliderimg3.jpg

691 ms

point.png

point.png

270 ms

sectionimg-1.jpg

sectionimg-1.jpg

356 ms

point2.png

point2.png

410 ms

point2.png

point2.png

970 ms

box1.png

box1.png

470 ms

box2.png

box2.png

648 ms

box3.png

box3.png

630 ms

goodyear_tyres.png

goodyear_tyres.png

683 ms

logo.png

logo.png

739 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

720 ms

SEO Factors

whoschecking.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoschecking.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Whoschecking.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

whoschecking.com

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