1.9 sec in total
172 ms
1.3 sec
385 ms
Click here to check amazing Lenni content. Otherwise, check out these important facts you probably never knew about lenni.info
Visit lenni.infoWe analyzed Lenni.info page load time and found that the first response time was 172 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.
lenni.info performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.9 s
13/100
25%
Value11.4 s
5/100
10%
Value80 ms
99/100
30%
Value0.012
100/100
15%
Value6.5 s
59/100
10%
172 ms
326 ms
85 ms
32 ms
77 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Lenni.info, 50% (15 requests) were made to Leonard.io and 20% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (458 ms) relates to the external source Leonard.io.
Page size can be reduced by 178.0 kB (18%)
996.5 kB
818.4 kB
In fact, the total size of Lenni.info main page is 996.5 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. 35% of websites need less resources to load. Images take 778.7 kB which makes up the majority of the site volume.
Potential reduce by 9.8 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 4.4 kB, which is 35% 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 9.8 kB or 77% of the original size.
Potential reduce by 23.2 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. Lenni images are well optimized though.
Potential reduce by 31.1 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 31.1 kB or 47% of the original size.
Potential reduce by 113.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. Lenni.info needs all CSS files to be minified and compressed as it can save up to 113.9 kB or 82% of the original size.
Number of requests can be reduced by 11 (58%)
19
8
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lenni. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lenni.info
172 ms
leonard.io
326 ms
85 ms
bootstrap.min.css
32 ms
main.css
77 ms
normalize.css
154 ms
component.css
232 ms
font-awesome.css
36 ms
jquery.min.js
74 ms
modernizr.custom.js
248 ms
css
61 ms
bootstrap.min.js
37 ms
retina.js
255 ms
classie.js
296 ms
gnmenu.js
296 ms
header-bg-2.jpg
458 ms
foliowrap.jpg
409 ms
sphere.png
307 ms
marktnavigator.png
416 ms
mint.jpg
248 ms
analytics.js
60 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
75 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
76 ms
wkfQbvfT_02e2IWO3yYueQ.woff
92 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
116 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
116 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
115 ms
fontawesome-webfont.woff
2 ms
ecoicons.woff
97 ms
collect
25 ms
lenni.info accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
lenni.info 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
Issues were logged in the Issues panel in Chrome Devtools
lenni.info 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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lenni.info can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Lenni.info 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.
lenni.info
Open Graph description is not detected on the main page of Lenni. 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: