Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

wes.io

Wes Bos - Full Stack Developer

Page Load Speed

1.3 sec in total

First Response

74 ms

Resources Loaded

303 ms

Page Rendered

938 ms

wes.io screenshot

About Website

Click here to check amazing Wes content. Otherwise, check out these important facts you probably never knew about wes.io

Visit wes.io

Key Findings

We analyzed Wes.io page load time and found that the first response time was 74 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

wes.io performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

wesbos.com

74 ms

BJS-Social-Share.png

136 ms

analytics.js

29 ms

whitegrit-3c286f3a0990b91b9f6bb97828dd3d2f.png

14 ms

blackgrit-6a2d636a530802d3ce97afb7af53a84b.png

27 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wes.io, 8% (1 request) were made to Res.cloudinary.com and 8% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (136 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 172.8 kB (27%)

Content Size

644.0 kB

After Optimization

471.2 kB

In fact, the total size of Wes.io main page is 644.0 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. 20% of websites need less resources to load. Images take 420.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 170.5 kB

  • Original 202.5 kB
  • After minification 202.3 kB
  • After compression 32.0 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.5 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 2.3 kB

  • Original 420.5 kB
  • After minification 418.3 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. Wes images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 6 (55%)

Requests Now

11

After Optimization

5

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

Accessibility Review

wes.io accessibility score

100

Accessibility Issues

Best Practices

wes.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wes.io SEO score

92

Search Engine Optimization Advices

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 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 Wes.io 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 Wes.io 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 Wes. 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: