721 ms in total
35 ms
521 ms
165 ms
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.coWe 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.
wtf.jefff.co performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.1 s
100/100
25%
Value1.1 s
100/100
10%
Value0 ms
100/100
30%
Value0.569
12/100
15%
Value2.3 s
99/100
10%
35 ms
30 ms
136 ms
7 ms
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 size can be reduced by 8.9 kB (21%)
43.2 kB
34.3 kB
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.
Potential reduce by 8.3 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.
Potential reduce by 563 B
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.
Potential reduce by 34 B
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.
We found no issues to fix!
5
5
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.
wtf.jefff.co
35 ms
app.css
30 ms
app.js
136 ms
ga.js
7 ms
jefff.jpg
101 ms
__utm.gif
21 ms
listeninto.png
30 ms
lTnujIfuO2uuefaZ77EFHnjkuSeeeuazhcFLL7x0ziKl9nujyGuLfVVil6WWWGaF5VY6Kt1qq2RYI9NaWdb5Itt6OTbItdE1x2y2SZ4tvvnuurfOu+Cdj9676JIrrrrrskL37HDLbTdCAmFJmRnpfwGBtWAxAAAA
3 ms
eu+iSK66667JC9+xwy203QgJhSZkZ6X8BgbVgMQAAAA==
2 ms
-riKkMjQB-Tz3xXCw54paQLUuEpTyoUstqEm5AMlJo4.woff
27 ms
nAKwuw6_dIh5kwvpj3ShNfesZW2xOQ-xsNqO47m55DA.woff
327 ms
ionicons.woff
28 ms
wtf.jefff.co accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
wtf.jefff.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wtf.jefff.co SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
wtf.jefff.co
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: