905 ms in total
27 ms
769 ms
109 ms
Welcome to lexi.se homepage info - get ready to check Lexi best content right away, or after learning these important things about lexi.se
Product strategist & designer with 20 years experience leading product teams and managing stakeholders through the entire lifecycle of shaping, building and evolving digital products.
Visit lexi.seWe analyzed Lexi.se page load time and found that the first response time was 27 ms and then it took 878 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
lexi.se performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value2.5 s
89/100
25%
Value1.4 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
27 ms
44 ms
14 ms
64 ms
25 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 13% of them (3 requests) were addressed to the original Lexi.se, 78% (18 requests) were made to Use.typekit.net and 4% (1 request) were made to Plausible.io. The less responsive or slowest element that took the longest time to load (548 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 6.4 kB (77%)
8.3 kB
1.9 kB
In fact, the total size of Lexi.se main page is 8.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. 35% of websites need less resources to load. HTML takes 8.3 kB which makes up the majority of the site volume.
Potential reduce by 6.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 6.4 kB or 77% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lexi. According to our analytics all requests are already optimized.
lexi.se
27 ms
plausible.js
44 ms
main.css
14 ms
irp6ewa.js
64 ms
application.js
25 ms
i
264 ms
i
167 ms
i
187 ms
i
263 ms
i
470 ms
i
155 ms
i
315 ms
i
180 ms
i
280 ms
i
458 ms
i
378 ms
i
339 ms
i
405 ms
i
442 ms
i
548 ms
i
439 ms
i
478 ms
p.gif
55 ms
lexi.se accessibility score
lexi.se best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
lexi.se 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
SV
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexi.se can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Swedish language. Our system also found out that Lexi.se 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.
lexi.se
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: