996 ms in total
40 ms
792 ms
164 ms
Welcome to leeboonstra.dev homepage info - get ready to check Lee Boonstra best content right away, or after learning these important things about leeboonstra.dev
Conversational AI Blog of SWE Tech Lead Lee Boonstra. Writes about Generative AI, Prompt Engineering, Dialogflow, Chatbots, NLP and AI in Contact Centers.
Visit leeboonstra.devWe analyzed Leeboonstra.dev page load time and found that the first response time was 40 ms and then it took 956 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
leeboonstra.dev performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value3.1 s
76/100
25%
Value5.1 s
62/100
10%
Value1,250 ms
19/100
30%
Value0
100/100
15%
Value11.1 s
20/100
10%
40 ms
95 ms
4 ms
18 ms
22 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 27% of them (16 requests) were addressed to the original Leeboonstra.dev, 35% (21 requests) were made to Encore.scdn.co and 28% (17 requests) were made to Embed-cdn.spotifycdn.com. The less responsive or slowest element that took the longest time to load (296 ms) relates to the external source Open.spotify.com.
Page size can be reduced by 42.2 kB (6%)
701.3 kB
659.1 kB
In fact, the total size of Leeboonstra.dev main page is 701.3 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. 75% 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. Javascripts take 529.4 kB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 73% of the original size.
Potential reduce by 17.4 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. Obviously, Lee Boonstra needs image optimization as it can save up to 17.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 333 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.
Potential reduce by 38 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. Leeboonstra.dev has all CSS files already compressed.
Number of requests can be reduced by 21 (62%)
34
13
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lee Boonstra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
leeboonstra.dev
40 ms
www.leeboonstra.dev
95 ms
main.css
4 ms
prism-atom-dark.css
18 ms
prism.js
22 ms
bundle.js
45 ms
js
87 ms
4uwFcwDRchAGSun4xLqxDB
296 ms
thumb_podcast4.png
162 ms
small_profile.jpg
6 ms
small_googlelogo.jpg
6 ms
small_apress-book.jpg
4 ms
thumb_prizes1.png
7 ms
thumb_0_dialogflow-book.png
12 ms
thumb_dialogflow_flutter.png
11 ms
thumb_dialogflow-cx-flows.png
12 ms
analytics.js
17 ms
collect
15 ms
bebasneue-webfont.woff
4 ms
AbhayaLibre-Regular-webfont.woff
7 ms
collect
22 ms
ga-audiences
27 ms
461cd0504da4fff1.css
17 ms
192261c9a6efeac6.css
19 ms
364d0cc114e2dc9d.css
22 ms
polyfills-c67a75d1b6f99dc8.js
32 ms
webpack-ea34bc3366caf997.js
31 ms
framework-9061fa2704610d1a.js
49 ms
main-45d0e026ad3339d5.js
48 ms
_app-410ecf0558dd409e.js
90 ms
fec483df-e793d3f4aac0c1fc.js
88 ms
594-284e2b73b8c68654.js
83 ms
396-5ce3af1ccb0ab43d.js
87 ms
745-def44b4adc358a13.js
89 ms
463-cd3bdc4b44e07b72.js
171 ms
%5Bid%5D-7ae0b1245e900524.js
172 ms
_buildManifest.js
180 ms
_ssgManifest.js
181 ms
CircularSpTitle-Bold-7cd3208b73fd0850bca5d8f7821439cd.woff
131 ms
CircularSpTitle-Black-b063ad0a42cbaf519c7ccba8b3e1caeb.woff
138 ms
CircularSpTitle-Tall-Bold-24c7e518b6e633e498760fab4aa88218.woff
143 ms
CircularSpTitle-Tall-Black-35a438fa59bc07bdf08133e438d72409.woff
157 ms
CircularSp-Arab-Book-15ab1b42ca6ef5894519756031ee3ed5.woff
143 ms
CircularSp-Arab-Bold-f6f9a0b56c26078440d40b145f48ab5a.woff
145 ms
CircularSp-Arab-Black-85253c80e7df46d62c4d5420e1cc5f4c.woff
142 ms
CircularSp-Hebr-Book-d8209975eafc81a9499df8401a339ddd.woff
144 ms
CircularSp-Hebr-Bold-caa03e4cb8690e726ef1625c7d91a7a5.woff
144 ms
CircularSp-Hebr-Black-f52613a9d541248805af1d0bb33102f8.woff
145 ms
CircularSp-Cyrl-Book-6f078f781ee313e298ad8997fd1ffe3d.woff
154 ms
CircularSp-Cyrl-Bold-7e54bccaf45728c472079785d5cd4519.woff
155 ms
CircularSp-Cyrl-Black-b4305d9bf82554f631d2636c3ef90c54.woff
155 ms
CircularSp-Grek-Book-c9de2c0741586c1ab7b6e95541fc7807.woff
155 ms
CircularSp-Grek-Bold-53bb923248ba22cf5554bbe5f434c5c8.woff
155 ms
CircularSp-Grek-Black-49883536c1a3bfc688235ce40572731d.woff
164 ms
CircularSp-Deva-Book-159c0e02bc9dc7dd0830fb569faf1069.woff
163 ms
CircularSp-Deva-Bold-a212adfa8f476d3544664463d5759178.woff
164 ms
CircularSp-Deva-Black-bbe191a7814d06a3eecc724265dae2d0.woff
164 ms
CircularSp-Book-4f217aebee53ffc72f4444f79041ffa5.woff
163 ms
CircularSp-Bold-79ebb2bdea919cebedea4884d08c499e.woff
164 ms
_error-2d285668fa3a339d.js
21 ms
leeboonstra.dev 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
leeboonstra.dev 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
General
Impact
Issue
Missing source maps for large first-party JavaScript
leeboonstra.dev SEO score
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 Leeboonstra.dev 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 Leeboonstra.dev 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.
leeboonstra.dev
Open Graph data is detected on the main page of Lee Boonstra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: