2.8 sec in total
371 ms
2.2 sec
231 ms
Click here to check amazing Erik Kaiser content. Otherwise, check out these important facts you probably never knew about erikkaiser.com
Global Program Strategy Manager & Tech Evangelist. San Francisco. The postings on this site are my own and don't necessarily represent my current, future, or past employer's positions, strat...
Visit erikkaiser.comWe analyzed Erikkaiser.com page load time and found that the first response time was 371 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
erikkaiser.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.4 s
21/100
25%
Value4.4 s
74/100
10%
Value170 ms
93/100
30%
Value0.012
100/100
15%
Value5.8 s
67/100
10%
371 ms
29 ms
35 ms
50 ms
44 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Erikkaiser.com, 18% (8 requests) were made to 41.media.tumblr.com and 18% (8 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source 41.media.tumblr.com.
Page size can be reduced by 420.6 kB (38%)
1.1 MB
689.0 kB
In fact, the total size of Erikkaiser.com main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 545.5 kB which makes up the majority of the site volume.
Potential reduce by 46.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. This page needs HTML code to be minified as it can gain 13.2 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 46.3 kB or 82% of the original size.
Potential reduce by 21.6 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. Erik Kaiser images are well optimized though.
Potential reduce by 351.8 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 351.8 kB or 64% of the original size.
Potential reduce by 896 B
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. Erikkaiser.com needs all CSS files to be minified and compressed as it can save up to 896 B or 58% of the original size.
Number of requests can be reduced by 13 (32%)
41
28
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Erik Kaiser. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
erikkaiser.com
371 ms
pre_tumblelog.js
29 ms
reset.css
35 ms
jquery.js
50 ms
jquery.scale.js
44 ms
jquery.masonry.js
35 ms
tumblelog_post_message_queue.js
34 ms
stylesheet.css
40 ms
twitter.js
43 ms
index.js
40 ms
bravo.json
35 ms
analytics.js
63 ms
bravo.json
270 ms
install_theme.png
22 ms
avatar_e60c5185ec75_128.png
64 ms
tumblr_o3pn9ph7MD1qzav8so1_250.jpg
256 ms
tumblr_o3cb5gh1Bd1qzav8so1_250.jpg
235 ms
tumblr_o2zqoujiWv1qzav8so1_250.jpg
14 ms
tumblr_o1fwu3rM8F1qzav8so1_250.jpg
242 ms
tumblr_o1fkfnPTq81qzav8so1_250.jpg
240 ms
tumblr_nyyikhgiBa1qzav8so1_250.jpg
240 ms
tumblr_o0ao3rGIRM1qzav8so1_250.jpg
241 ms
portrait-mask-128.png
6 ms
search.png
8 ms
tumblr_o1fdgudTkt1qzav8so1_250.jpg
36 ms
tumblr_nzm431tBDW1qzav8so1_250.jpg
37 ms
tumblr_nzjwt3y2Zk1qzav8so1_250.jpg
37 ms
tumblr_nzh7qsGgIx1qzav8so1_250.jpg
38 ms
tumblr_nza754QAZV1qzav8so1_250.jpg
45 ms
tumblr_nxkm51cIQ01qzav8so1_250.jpg
37 ms
tumblr_nx0iegYOCl1qzav8so1_250.jpg
1673 ms
blogger.js
226 ms
collect
17 ms
impixu
179 ms
impixu
32 ms
analytics.html
51 ms
login_check.html
16 ms
rapid-3.36.js
58 ms
rapidworker-1.2.js
66 ms
ga.js
101 ms
analytics.js
92 ms
cs.js
46 ms
yql
230 ms
__utm.gif
15 ms
cedexis.radar.js
4 ms
erikkaiser.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
erikkaiser.com 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
erikkaiser.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Erikkaiser.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 Erikkaiser.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.
erikkaiser.com
Open Graph data is detected on the main page of Erik Kaiser. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: