Tools & Wizards About Us
whyfiles.org screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    71% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

whyfiles.org

The Why Files | The Science Behind the News

Page Load Speed

3.6 sec in total

First Response

1.1 sec

Resources Loaded

2.4 sec

Page Rendered

149 ms

whyfiles.org screenshot

About Website

Click here to check amazing Why Files content for United States. Otherwise, check out these important facts you probably never knew about whyfiles.org

Your source for science behind the news.

Visit whyfiles.org

Key Findings

We analyzed Whyfiles.org page load time and found that the first response time was 1.1 sec and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster. This domain responded with an error, which can significantly jeopardize Whyfiles.org rating and web reputation

Performance Metrics

whyfiles.org performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

whyfiles.org

1117 ms

style.css

217 ms

moztheme2011.css

76 ms

wgs.css

62 ms

cat-posts.css

72 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 76% of them (58 requests) were addressed to the original Whyfiles.org, 7% (5 requests) were made to Google.com and 4% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whyfiles.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 609.7 kB (29%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whyfiles.org main page is 2.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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 37.1 kB

  • Original 47.7 kB
  • After minification 46.3 kB
  • After compression 10.6 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 37.1 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 42.5 kB

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

JavaScript Optimization

-68%

Potential reduce by 276.3 kB

  • Original 407.2 kB
  • After minification 356.5 kB
  • After compression 130.8 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 276.3 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 253.7 kB

  • Original 301.7 kB
  • After minification 250.7 kB
  • After compression 48.0 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. Whyfiles.org needs all CSS files to be minified and compressed as it can save up to 253.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (60%)

Requests Now

72

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Files. 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 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whyfiles.org

whyfiles.org

1117 ms

style.css

style.css

217 ms

moztheme2011.css

moztheme2011.css

76 ms

wgs.css

wgs.css

62 ms

cat-posts.css

cat-posts.css

72 ms

style-1.css

style-1.css

214 ms

social_widget.css

social_widget.css

108 ms

css

css

21 ms

quotes-collection.css

quotes-collection.css

131 ms

style.css

style.css

131 ms

shortcodes.css

shortcodes.css

169 ms

jetpack.css

jetpack.css

252 ms

owl.carousel.css

owl.carousel.css

195 ms

owl.theme.css

owl.theme.css

195 ms

owl.transitions.css

owl.transitions.css

228 ms

styles.css

styles.css

247 ms

lightbox.min.css

lightbox.min.css

252 ms

jquery.js

jquery.js

398 ms

jquery-migrate.min.js

jquery-migrate.min.js

283 ms

img-mouseover.js

img-mouseover.js

285 ms

quotes-collection.js

quotes-collection.js

306 ms

easy-spoiler.js

easy-spoiler.js

323 ms

owl.carousel.js

owl.carousel.js

427 ms

script.js

script.js

340 ms

easy-spoiler.css

easy-spoiler.css

343 ms

dz50r47e.js

dz50r47e.js

79 ms

style.css

style.css

311 ms

google_cse_v2.js

google_cse_v2.js

328 ms

devicepx-jetpack.js

devicepx-jetpack.js

3 ms

gprofiles.js

gprofiles.js

4 ms

wpgroho.js

wpgroho.js

345 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

360 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

369 ms

twentyeleven.js

twentyeleven.js

469 ms

fv-flowplayer.min.js

fv-flowplayer.min.js

590 ms

e-201607.js

e-201607.js

3 ms

style.css

style.css

389 ms

ga.js

ga.js

66 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

92 ms

twf_logo285.png

twf_logo285.png

61 ms

685feature_whyfiles_wrapup2.jpg

685feature_whyfiles_wrapup2.jpg

205 ms

slider-light-desc-bg.png

slider-light-desc-bg.png

79 ms

685prairie_vole.jpg

685prairie_vole.jpg

250 ms

685fruitflyflight.jpg

685fruitflyflight.jpg

219 ms

685feature_beeswax.jpg

685feature_beeswax.jpg

373 ms

search.png

search.png

123 ms

homepg_whyfiles_wrapup.jpg

homepg_whyfiles_wrapup.jpg

312 ms

homepg_vole_promiscuity.jpg

homepg_vole_promiscuity.jpg

443 ms

homepg_fruitfly_flight.jpg

homepg_fruitfly_flight.jpg

386 ms

homepg_beeswax.jpg

homepg_beeswax.jpg

470 ms

facebook.png

facebook.png

312 ms

twitter.png

twitter.png

370 ms

rss.png

rss.png

384 ms

email.png

email.png

430 ms

twf_greatest_hits_white.png

twf_greatest_hits_white.png

432 ms

feature_animal_love.jpg

feature_animal_love.jpg

561 ms

homepg_science_videos.jpg

homepg_science_videos.jpg

632 ms

bk_review300.png

bk_review300.png

575 ms

csis300.png

csis300.png

612 ms

weather_guys300.png

weather_guys300.png

584 ms

teaching300.png

teaching300.png

587 ms

interactives300.png

interactives300.png

707 ms

whytv300.png

whytv300.png

717 ms

printfriendly.js

printfriendly.js

38 ms

cse.js

cse.js

38 ms

slider-light-desc-bg.png

slider-light-desc-bg.png

620 ms

__utm.gif

__utm.gif

22 ms

cse.js

cse.js

85 ms

hovercard.css

hovercard.css

21 ms

services.css

services.css

22 ms

g.gif

g.gif

13 ms

jsapi

jsapi

27 ms

default+en.css

default+en.css

2 ms

default.css

default.css

25 ms

default+en.I.js

default+en.I.js

8 ms

default.css

default.css

13 ms

Accessibility Review

whyfiles.org accessibility score

83

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

whyfiles.org best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

whyfiles.org SEO score

70

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use 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 Whyfiles.org 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 Whyfiles.org 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

whyfiles.org

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