Access fourhourblog.com. The Blog of Author Tim Ferriss - Tim Ferriss is the author of five #1 New York Times bestsellers and...

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value2,600 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.122

84/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

33 ms

2629490064.js

298 ms

128 ms

reveal.css

127 ms

141 ms

Our browser made a total of 241 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fourhourblog.com, 6% (14 requests) were made to Html5-player.libsyn.com and 5% (12 requests) were made to Wpcomwidgets.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Servedby.flashtalking.com.

Content Size

3.6 MB

After Optimization

1.9 MB

In fact, the total size of Fourhourblog.com main page is 3.6 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. 80% 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 170.3 kB

Original 224.9 kB
After minification 220.2 kB
After compression 54.7 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 170.3 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 19.4 kB

Original 1.4 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. Fourhour Blog images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 813.7 kB

Original 1.2 MB
After minification 1.1 MB
After compression 369.4 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 813.7 kB or 69% of the original size.

CSS Optimization

-92%

Potential reduce by 725.8 kB

Original 791.0 kB
After minification 786.2 kB
After compression 65.2 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. Fourhourblog.com needs all CSS files to be minified and compressed as it can save up to 725.8 kB or 92% of the original size.

Requests Now

226

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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/).

High

Document uses 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 Fourhourblog.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 Fourhourblog.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

Open Graph description is not detected on the main page of Fourhour Blog. 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: