Tools & Wizards About Us
whythings.net screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

whythings.net

From Brexit to Fixit – Why Britain is Getting Poorer (and what we should do about it)

Page Load Speed

3.7 sec in total

First Response

1.3 sec

Resources Loaded

1.8 sec

Page Rendered

619 ms

whythings.net screenshot

About Website

Visit whythings.net now to see the best up-to-date Whythings content and also check out these interesting facts you probably never knew about whythings.net

An inquiry into wealth, work and values — a book about global economics, money, debt and the financialization of the world economy, mike roscoe

Visit whythings.net

Key Findings

We analyzed Whythings.net page load time and found that the first response time was 1.3 sec and then it took 2.4 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.

Performance Metrics

whythings.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

whythings.net

1345 ms

artsgraphiquess.css

84 ms

WhyThings_banner.jpg

405 ms

WhyThingsBook.jpg

233 ms

DannyDorlingQuote.jpg

402 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that all of those requests were addressed to Whythings.net and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whythings.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.4 kB (10%)

Content Size

352.3 kB

After Optimization

317.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Whythings.net main page is 352.3 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. Only 10% of websites need less resources to load. Images take 337.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 9.2 kB

  • Original 13.1 kB
  • After minification 13.1 kB
  • After compression 3.9 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 9.2 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 24.0 kB

  • Original 337.7 kB
  • After minification 313.6 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. Whythings images are well optimized though.

CSS Optimization

-74%

Potential reduce by 1.1 kB

  • Original 1.5 kB
  • After minification 1.2 kB
  • After compression 392 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. Whythings.net needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • Images
  • CSS

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whythings. According to our analytics all requests are already optimized.

Network Requests Diagram

whythings.net

whythings.net

1345 ms

artsgraphiquess.css

artsgraphiquess.css

84 ms

WhyThings_banner.jpg

WhyThings_banner.jpg

405 ms

WhyThingsBook.jpg

WhyThingsBook.jpg

233 ms

DannyDorlingQuote.jpg

DannyDorlingQuote.jpg

402 ms

MikeCrawshawQuote.jpg

MikeCrawshawQuote.jpg

401 ms

Ten_charts.jpg

Ten_charts.jpg

400 ms

Accessibility Review

whythings.net accessibility score

78

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

whythings.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

whythings.net SEO score

67

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whythings.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whythings.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

whythings.net

Open Graph description is not detected on the main page of Whythings. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: