Tools & Wizards About Us
thewhy.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

thewhy.com

thewhy.com| 502: Bad gateway

Page Load Speed

3.9 sec in total

First Response

670 ms

Resources Loaded

2.4 sec

Page Rendered

829 ms

thewhy.com screenshot

About Website

Welcome to thewhy.com homepage info - get ready to check Thewhy best content for United States right away, or after learning these important things about thewhy.com

News, Views & Opinions

Visit thewhy.com

Key Findings

We analyzed Thewhy.com page load time and found that the first response time was 670 ms and then it took 3.2 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

thewhy.com performance score

0

Network Requests Diagram

www.thewhy.com

670 ms

wp-emoji-release.min.js

132 ms

bootstrap.css

233 ms

shortcodes.css

152 ms

tp_twitter_plugin.css

153 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 95% of them (78 requests) were addressed to the original Thewhy.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (709 ms) belongs to the original domain Thewhy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 655.8 kB (16%)

Content Size

4.1 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thewhy.com main page is 4.1 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 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 88.6 kB

  • Original 103.1 kB
  • After minification 88.1 kB
  • After compression 14.5 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 15.0 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 88.6 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 41.1 kB

  • Original 3.3 MB
  • After minification 3.3 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. Thewhy images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 234.6 kB

  • Original 349.2 kB
  • After minification 311.9 kB
  • After compression 114.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 234.6 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 291.6 kB

  • Original 341.1 kB
  • After minification 288.5 kB
  • After compression 49.5 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. Thewhy.com needs all CSS files to be minified and compressed as it can save up to 291.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (36%)

Requests Now

80

After Optimization

51

  • Images
  • JavaScript
  • CSS

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thewhy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 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.thewhy.com

www.thewhy.com

670 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

132 ms

bootstrap.css

bootstrap.css

233 ms

shortcodes.css

shortcodes.css

152 ms

tp_twitter_plugin.css

tp_twitter_plugin.css

153 ms

style.css

style.css

160 ms

css

css

24 ms

jquery.js

jquery.js

245 ms

jquery-migrate.min.js

jquery-migrate.min.js

203 ms

bootstrap.js

bootstrap.js

227 ms

init.js

init.js

228 ms

retina.js

retina.js

190 ms

isotope.js

isotope.js

257 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

256 ms

manual-trigger.js

manual-trigger.js

255 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

268 ms

custom.js

custom.js

271 ms

jquery.fitvids.js

jquery.fitvids.js

300 ms

jquery.sidr.min.js

jquery.sidr.min.js

331 ms

superfishmenu.js

superfishmenu.js

331 ms

hoverintent.js

hoverintent.js

331 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

350 ms

jquery.flexslider.js

jquery.flexslider.js

349 ms

navie.js

navie.js

374 ms

isotopeme-auto.js

isotopeme-auto.js

405 ms

bootstrap.min.js

bootstrap.min.js

407 ms

wp-embed.min.js

wp-embed.min.js

406 ms

bootstrap.css

bootstrap.css

328 ms

sfmenu.css

sfmenu.css

325 ms

media.css

media.css

344 ms

jquery.sidr.dark.css

jquery.sidr.dark.css

377 ms

analytics.js

analytics.js

125 ms

logo-012.png

logo-012.png

90 ms

responsive.png

responsive.png

91 ms

searchicon.png

searchicon.png

90 ms

facebook.png

facebook.png

91 ms

twitter.png

twitter.png

91 ms

google.png

google.png

92 ms

5-Star-Treatment.jpg

5-Star-Treatment.jpg

502 ms

icon2.png

icon2.png

500 ms

icon1.png

icon1.png

499 ms

JNU-Issue-1.jpg

JNU-Issue-1.jpg

501 ms

JNU-Issue.jpg

JNU-Issue.jpg

502 ms

JNU.jpg

JNU.jpg

502 ms

Sleepless-man.jpg

Sleepless-man.jpg

503 ms

North-Korea.jpg

North-Korea.jpg

504 ms

Lance-Naik.jpg

Lance-Naik.jpg

505 ms

INDIAN-RACISM.jpg

INDIAN-RACISM.jpg

505 ms

Sikhs-Regiment.jpg

Sikhs-Regiment.jpg

506 ms

Priyanka-Vadra.jpg

Priyanka-Vadra.jpg

506 ms

MALDA-VIOLENCE.jpg

MALDA-VIOLENCE.jpg

529 ms

US-Elections.jpg

US-Elections.jpg

527 ms

Tennis-1.jpg

Tennis-1.jpg

527 ms

Cupid.jpg

Cupid.jpg

533 ms

Rohith-Vemula.jpg

Rohith-Vemula.jpg

566 ms

Homs.jpg

Homs.jpg

567 ms

Bernie-Sanders.jpg

Bernie-Sanders.jpg

591 ms

Madaya.jpg

Madaya.jpg

600 ms

Chris-Gayle.jpg

Chris-Gayle.jpg

599 ms

Climate-Change.jpg

Climate-Change.jpg

609 ms

Freezing-Syrian-Child.jpg

Freezing-Syrian-Child.jpg

631 ms

Rahat-Fateh-Ali-Khan.jpg

Rahat-Fateh-Ali-Khan.jpg

634 ms

Dsesh.jpg

Dsesh.jpg

666 ms

Modi-Nawaz-1.jpg

Modi-Nawaz-1.jpg

678 ms

Syrian-Refugees-1.jpg

Syrian-Refugees-1.jpg

677 ms

NIRBHAYA.jpg

NIRBHAYA.jpg

686 ms

BJP.jpg

BJP.jpg

709 ms

Seasons-Grettings.jpg

Seasons-Grettings.jpg

632 ms

GCC-Summit.jpg

GCC-Summit.jpg

660 ms

Indian-Parliament-House.jpg

Indian-Parliament-House.jpg

673 ms

Delhi-Traffic.jpg

Delhi-Traffic.jpg

669 ms

RACIAL-PROFILING.jpg

RACIAL-PROFILING.jpg

680 ms

Vladimir-Putin1.jpg

Vladimir-Putin1.jpg

707 ms

GOA.jpg

GOA.jpg

298 ms

Dangerous-Sandwich.jpg

Dangerous-Sandwich.jpg

324 ms

loadme.gif

loadme.gif

338 ms

tweet.png

tweet.png

337 ms

facebook.png

facebook.png

348 ms

twitter.png

twitter.png

373 ms

googleplus.png

googleplus.png

372 ms

collect

collect

12 ms

EAqh528fFdbUek8UOky4sA.woff

EAqh528fFdbUek8UOky4sA.woff

8 ms

SEO Factors

thewhy.com SEO score

0

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 Thewhy.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 Thewhy.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

thewhy.com

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