Tools & Wizards About Us

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

wtf.jefff.co

made by Jefff | Web Designer and Front-end Tinkerer. Music Snob. Father. Husband. Nerd.

Page Load Speed

721 ms in total

First Response

35 ms

Resources Loaded

521 ms

Page Rendered

165 ms

About Website

Click here to check amazing Wtf Jefff content. Otherwise, check out these important facts you probably never knew about wtf.jefff.co

The web sandbox of Jefff Doan; my work, my musings on web design, email design, and other web-related thingamajigs.

Visit wtf.jefff.co

Key Findings

We analyzed Wtf.jefff.co page load time and found that the first response time was 35 ms and then it took 686 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

wtf.jefff.co performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.569

12/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

wtf.jefff.co

35 ms

app.css

30 ms

app.js

136 ms

ga.js

7 ms

jefff.jpg

101 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 50% of them (6 requests) were addressed to the original Wtf.jefff.co, 17% (2 requests) were made to Google-analytics.com and 17% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (327 ms) relates to the external source Themes.googleusercontent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.9 kB (21%)

Content Size

43.2 kB

After Optimization

34.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wtf.jefff.co main page is 43.2 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. 30% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 8.3 kB

  • Original 14.3 kB
  • After minification 13.2 kB
  • After compression 6.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 8.3 kB or 58% of the original size.

Image Optimization

-5%

Potential reduce by 563 B

  • Original 11.7 kB
  • After minification 11.2 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. Wtf Jefff images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

wtf.jefff.co accessibility score

74

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

wtf.jefff.co best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wtf.jefff.co SEO score

92

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

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 uses legible font sizes

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 Wtf.jefff.co 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 Wtf.jefff.co 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 Wtf Jefff. 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: