1.8 sec in total
111 ms
1.6 sec
157 ms
Click here to check amazing Chrislarson content for India. Otherwise, check out these important facts you probably never knew about chrislarson.me
Building a Well Architected Life one habit at a time.
Visit chrislarson.meWe analyzed Chrislarson.me page load time and found that the first response time was 111 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
chrislarson.me performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value2.5 s
89/100
25%
Value1.3 s
100/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value2.6 s
98/100
10%
111 ms
704 ms
91 ms
32 ms
44 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 50% of them (23 requests) were addressed to the original Chrislarson.me, 11% (5 requests) were made to Pagead2.googlesyndication.com and 9% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (704 ms) belongs to the original domain Chrislarson.me.
Page size can be reduced by 258.6 kB (55%)
474.4 kB
215.8 kB
In fact, the total size of Chrislarson.me main page is 474.4 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. 40% of websites need less resources to load. Javascripts take 269.0 kB which makes up the majority of the site volume.
Potential reduce by 16.1 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 16.1 kB or 75% of the original size.
Potential reduce by 1.0 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. Chrislarson images are well optimized though.
Potential reduce by 139.4 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 139.4 kB or 52% of the original size.
Potential reduce by 102.1 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. Chrislarson.me needs all CSS files to be minified and compressed as it can save up to 102.1 kB or 82% of the original size.
Number of requests can be reduced by 29 (69%)
42
13
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chrislarson. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
chrislarson.me
111 ms
system.base.css
704 ms
codefilter.css
91 ms
field.css
32 ms
fitvids.css
44 ms
views.css
28 ms
colorbox_style.css
51 ms
ctools.css
62 ms
bootstrap.min.css
7 ms
overrides.css
46 ms
jquery.min.js
136 ms
jquery.once.js
83 ms
drupal.js
84 ms
jquery.fitvids.js
88 ms
bootstrap.min.js
9 ms
codefilter.js
315 ms
fitvids.js
97 ms
media_colorbox.js
128 ms
jquery.colorbox-min.js
100 ms
colorbox.js
210 ms
colorbox_style.js
128 ms
googleanalytics.js
160 ms
adsbygoogle.js
8 ms
bootstrap.js
140 ms
analytics.js
25 ms
Profile-250px.png
54 ms
ca-pub-8923873743868053.js
126 ms
zrt_lookup.html
55 ms
show_ads_impl.js
63 ms
collect
41 ms
collect
133 ms
ads
319 ms
osd.js
8 ms
ads
317 ms
css
56 ms
m_js_controller.js
73 ms
abg.js
101 ms
favicon
87 ms
favicon
100 ms
googlelogo_color_112x36dp.png
53 ms
nessie_icon_tiamat_white.png
50 ms
s
32 ms
x_button_blue2.png
14 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
8 ms
PuwvqkdbcqU-fCZ9Ed-b7cDdSZkkecOE1hvV7ZHvhyU.ttf
49 ms
ui
57 ms
chrislarson.me 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
chrislarson.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
chrislarson.me 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 Chrislarson.me 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 Chrislarson.me 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.
chrislarson.me
Open Graph description is not detected on the main page of Chrislarson. 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: