Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

5.7 sec in total

First Response

251 ms

Resources Loaded

4.9 sec

Page Rendered

583 ms

lexs.org screenshot

About Website

Welcome to lexs.org homepage info - get ready to check Lexs best content for Germany right away, or after learning these important things about lexs.org

Visit lexs.org

Key Findings

We analyzed Lexs.org page load time and found that the first response time was 251 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

lexs.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

lexs.org

251 ms

www.lexs.org

2507 ms

reset.css

201 ms

template.css

294 ms

joomla.css

299 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 54% of them (50 requests) were addressed to the original Lexs.org, 25% (23 requests) were made to Maps.googleapis.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Lexs.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 567.4 kB (33%)

Content Size

1.7 MB

After Optimization

1.1 MB

In fact, the total size of Lexs.org main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 903.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 48.4 kB

  • Original 57.1 kB
  • After minification 56.0 kB
  • After compression 8.7 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 48.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 9.9 kB

  • Original 903.4 kB
  • After minification 893.5 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. Lexs images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 435.1 kB

  • Original 653.5 kB
  • After minification 652.0 kB
  • After compression 218.3 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 435.1 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 73.9 kB

  • Original 91.2 kB
  • After minification 80.8 kB
  • After compression 17.3 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. Lexs.org needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (39%)

Requests Now

82

After Optimization

50

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lexs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

lexs.org accessibility score

71

Accessibility Issues

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

High

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

lexs.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

lexs.org SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexs.org 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 German. Our system also found out that Lexs.org 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

Open Graph description is not detected on the main page of Lexs. 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: