6.4 sec in total
85 ms
4.3 sec
2 sec
Click here to check amazing What I Learnt content. Otherwise, check out these important facts you probably never knew about whatilearnt.today
One Thing Each Day by Tony Lembke
Visit whatilearnt.todayWe analyzed Whatilearnt.today page load time and found that the first response time was 85 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whatilearnt.today performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.7 s
8/100
25%
Value16.5 s
0/100
10%
Value1,480 ms
14/100
30%
Value0.389
26/100
15%
Value20.0 s
2/100
10%
85 ms
653 ms
32 ms
139 ms
198 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 63% of them (77 requests) were addressed to the original Whatilearnt.today, 10% (12 requests) were made to Wiltme2.files.wordpress.com and 7% (8 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source I0.wp.com.
Page size can be reduced by 1.7 MB (61%)
2.9 MB
1.1 MB
In fact, the total size of Whatilearnt.today main page is 2.9 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. 85% 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. CSS take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 156.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 156.7 kB or 79% of the original size.
Potential reduce by 21.8 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. What I Learnt images are well optimized though.
Potential reduce by 726.7 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 726.7 kB or 72% of the original size.
Potential reduce by 833.9 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. Whatilearnt.today needs all CSS files to be minified and compressed as it can save up to 833.9 kB or 82% of the original size.
Number of requests can be reduced by 53 (52%)
101
48
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What I Learnt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
whatilearnt.today
85 ms
whatilearnt.today
653 ms
style.css
32 ms
style.min.css
139 ms
style.min.css
198 ms
css
172 ms
style.min.css
172 ms
style.min.css
170 ms
style.min.css
169 ms
blocks.style.build.css
171 ms
shortcodes.css
164 ms
addthis_wordpress_public.min.css
219 ms
social-logos.min.css
223 ms
jetpack.css
229 ms
jquery.fancybox-1.3.4.css
213 ms
page_templates.css
214 ms
admin-ajax.php
783 ms
addthis_widget.js
219 ms
jquery.js
497 ms
jquery-migrate.min.js
222 ms
swarmdetect.js
221 ms
slider.js
218 ms
superfish.js
254 ms
css
200 ms
mediaelementplayer-legacy.min.css
472 ms
wp-mediaelement.min.css
256 ms
style.css
258 ms
twitter-timeline.min.js
256 ms
common.js
256 ms
jquery.easing-1.3.pack.js
549 ms
jquery.fancybox-1.3.4.pack.js
262 ms
et-ptemplates-frontend.js
263 ms
wp-embed.min.js
262 ms
spin.min.js
263 ms
jquery.spin.min.js
262 ms
jetpack-carousel.min.js
262 ms
mediaelement-and-player.min.js
280 ms
mediaelement-migrate.min.js
279 ms
wp-mediaelement.min.js
280 ms
jquery.uniform.min.js
285 ms
custom.js
285 ms
e-202044.js
205 ms
idle-timer.min.js
293 ms
sharing.min.js
242 ms
wp-emoji-release.min.js
197 ms
moatframe.js
721 ms
avatar.png
692 ms
nFVHaus_pjI
1155 ms
p193.jpg
798 ms
pduBdD5hbyY
1644 ms
GklP0ATsEtw
1934 ms
LU_KD1enR3Q
1908 ms
axis.png
1088 ms
New_Zealand.gif
864 ms
g_wallet_vision.jpg
708 ms
louis_xiv_of_france.png
829 ms
insano.jpg
829 ms
bg.jpg
543 ms
search.gif
436 ms
dropdown-search.gif
436 ms
profile_image.png
520 ms
delete.gif
435 ms
stamp.png
435 ms
bullet.gif
541 ms
be_kind.jpeg
388 ms
dustyesky.jpg
542 ms
times-uncertain-1024x504.png
541 ms
quick_brown_fox-1024x277.png
540 ms
yak.jpg
542 ms
world_bee_day.png
541 ms
thesquiz.png
541 ms
head-large.png
666 ms
dropdown-about.gif
540 ms
tony_ipad.jpg
539 ms
orange-medium.png
539 ms
be_kind-45x45.jpeg
665 ms
dustyesky-45x45.jpg
678 ms
times-uncertain-45x45.png
677 ms
yak-45x45.jpg
676 ms
2D453D1A-A2ED-4ACA-916B-F5135671483E-45x45.jpeg
676 ms
favicon-44x44.png
677 ms
loading.gif
821 ms
image-5.jpeg
2138 ms
lenin.jpg
1526 ms
swarmcdn.js
535 ms
Casino_Hand-webfont.woff
702 ms
wcYJIEUIwMaAAArwwHdAAA=
84 ms
social-logos.eot
465 ms
be_kind.jpeg
1166 ms
quick_brown_fox-1024x277.png
514 ms
times-uncertain-1024x504.png
1103 ms
dustyesky.jpg
1011 ms
thesquiz.png
991 ms
world_bee_day.png
1030 ms
yak.jpg
1091 ms
layers.33f5b85045a5f2308467.js
284 ms
head-large.png
938 ms
queen.jpg
962 ms
g_wallet_vision.jpg
954 ms
p193.jpg
1135 ms
widgets.js
1153 ms
santiago_de_compostela.png
1418 ms
avatar.png
916 ms
sdk.js
938 ms
ted_logo.gif
944 ms
spacepen.jpg
1087 ms
louis_xiv_of_france.png
1345 ms
insano.jpg
1343 ms
mem8YaGs126MiZpBA-UFVZ0e.ttf
1010 ms
mem5YaGs126MiZpBA-UN7rgOUuhs.ttf
1276 ms
300lo.json
1286 ms
www-player.css
654 ms
www-embed-player.js
707 ms
base.js
1008 ms
fetch-polyfill.js
803 ms
mejs-controls.svg
592 ms
dbf59f07-d494-4aa0-ad00-5a9be31b7052.js
782 ms
sh.f48a1a04fe8dbf021b4cda1d.html
175 ms
sdk.js
487 ms
widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html
237 ms
video-js.css
160 ms
id
25 ms
ad_status.js
20 ms
whatilearnt.today 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.
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
whatilearnt.today best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
whatilearnt.today SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatilearnt.today 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 Whatilearnt.today 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.
whatilearnt.today
Open Graph data is detected on the main page of What I Learnt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: