Tools & Wizards About Us
whytheycalled.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whytheycalled.com

Page Load Speed

5.5 sec in total

First Response

679 ms

Resources Loaded

4.1 sec

Page Rendered

704 ms

whytheycalled.com screenshot

About Website

Visit whytheycalled.com now to see the best up-to-date Whytheycalled content for United States and also check out these interesting facts you probably never knew about whytheycalled.com

Find out why you received a call with Reverse Phone Number Lookup! Leave a comment or file a complaint against offenders.

Visit whytheycalled.com

Key Findings

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

Performance Metrics

whytheycalled.com performance score

0

Network Requests Diagram

www.whytheycalled.com

679 ms

css

24 ms

wp-emoji-release.min.js

1073 ms

bwp-recent-comments.css

1409 ms

css

14 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 40% of them (23 requests) were addressed to the original Whytheycalled.com, 40% (23 requests) were made to I2.wp.com and 10% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Whytheycalled.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 607.0 kB (77%)

Content Size

788.4 kB

After Optimization

181.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whytheycalled.com main page is 788.4 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. 40% of websites need less resources to load. CSS take 364.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 68.0 kB

  • Original 86.1 kB
  • After minification 84.1 kB
  • After compression 18.1 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 68.0 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 2.0 kB

  • Original 23.2 kB
  • After minification 21.2 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. Whytheycalled images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 217.5 kB

  • Original 314.8 kB
  • After minification 270.1 kB
  • After compression 97.3 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 217.5 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 319.5 kB

  • Original 364.2 kB
  • After minification 326.3 kB
  • After compression 44.8 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. Whytheycalled.com needs all CSS files to be minified and compressed as it can save up to 319.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (88%)

Requests Now

51

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.whytheycalled.com

www.whytheycalled.com

679 ms

css

css

24 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1073 ms

bwp-recent-comments.css

bwp-recent-comments.css

1409 ms

css

css

14 ms

css

css

25 ms

style.css

style.css

1408 ms

style.css

style.css

2471 ms

shortcodes.css

shortcodes.css

203 ms

shortcodes_responsive.css

shortcodes_responsive.css

2539 ms

jquery.js

jquery.js

331 ms

jquery-migrate.min.js

jquery-migrate.min.js

375 ms

bwp-rc-ajax.js

bwp-rc-ajax.js

419 ms

jscripts.php

jscripts.php

466 ms

comment-reply.min.js

comment-reply.min.js

397 ms

jquery.fitvids.js

jquery.fitvids.js

442 ms

waypoints.min.js

waypoints.min.js

486 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

529 ms

custom.js

custom.js

618 ms

smoothscroll.js

smoothscroll.js

661 ms

jscripts-ftr-min.js

jscripts-ftr-min.js

705 ms

style.css

style.css

263 ms

ga.js

ga.js

177 ms

bkg_home.jpg

bkg_home.jpg

135 ms

wtc_logo.png

wtc_logo.png

132 ms

icon_comment.png

icon_comment.png

130 ms

avatar.png

avatar.png

44 ms

avatar.png

avatar.png

44 ms

avatar.png

avatar.png

44 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

43 ms

avatar.png

avatar.png

43 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

248 ms

avatar.png

avatar.png

42 ms

avatar.png

avatar.png

41 ms

avatar.png

avatar.png

40 ms

avatar.png

avatar.png

246 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

40 ms

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

40 ms

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

41 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

41 ms

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

40 ms

Lqv9ztoTUV8Q0FmQZzPqaDZ8Xgu54OUP9A9ig-MN_aY.ttf

Lqv9ztoTUV8Q0FmQZzPqaDZ8Xgu54OUP9A9ig-MN_aY.ttf

40 ms

ETmodules_v2.ttf

ETmodules_v2.ttf

221 ms

__utm.gif

__utm.gif

73 ms

nr-768.min.js

nr-768.min.js

45 ms

SEO Factors

whytheycalled.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 Whytheycalled.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 Whytheycalled.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

whytheycalled.com

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