Tools & Wizards About Us
lexi.se screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

lexi.se

Alexis Fellenius Makrigianni – product strategist & designer

Page Load Speed

1.1 sec in total

First Response

164 ms

Resources Loaded

845 ms

Page Rendered

67 ms

lexi.se screenshot

About Website

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.se

Key Findings

We analyzed Lexi.se page load time and found that the first response time was 164 ms and then it took 912 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.

Performance Metrics

lexi.se performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

lexi.se

164 ms

plausible.js

21 ms

main.css

26 ms

irp6ewa.js

230 ms

application.js

19 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 20% of them (3 requests) were addressed to the original Lexi.se, 67% (10 requests) were made to Use.typekit.net and 7% (1 request) were made to Plausible.io. The less responsive or slowest element that took the longest time to load (306 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.8 kB (74%)

Content Size

10.5 kB

After Optimization

2.7 kB

  • HTML
  • JavaScript

In fact, the total size of Lexi.se main page is 10.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. 15% of websites need less resources to load. HTML takes 9.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 7.8 kB

  • Original 9.8 kB
  • After minification 9.5 kB
  • After compression 1.9 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 7.8 kB or 80% of the original size.

JavaScript Optimization

-2%

Potential reduce by 15 B

  • Original 773 B
  • After minification 773 B
  • After compression 758 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.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 5 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.

Network Requests Diagram

lexi.se

lexi.se

164 ms

plausible.js

plausible.js

21 ms

main.css

main.css

26 ms

irp6ewa.js

irp6ewa.js

230 ms

application.js

application.js

19 ms

d

d

68 ms

d

d

84 ms

d

d

306 ms

d

d

222 ms

d

d

133 ms

d

d

151 ms

d

d

92 ms

d

d

277 ms

d

d

138 ms

p.gif

p.gif

20 ms

Accessibility Review

lexi.se accessibility score

100

Accessibility Issues

Best Practices

lexi.se best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

lexi.se SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    SV

  • Encoding

    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.

Social Sharing Optimization

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: