Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

lexxus.sk

LEXXUS a.s., Bratislava | Experti na nehnuteľnosti

Page Load Speed

9.2 sec in total

First Response

407 ms

Resources Loaded

8.2 sec

Page Rendered

545 ms

lexxus.sk screenshot

About Website

Click here to check amazing LEXXUS content for Slovakia. Otherwise, check out these important facts you probably never knew about lexxus.sk

Sme realitná kancelária, ktorá pôsobí na trhu už vyše 15 rokov. Našim hlavným cieľom je byť aj naďalej vašim spoľahlivým partnerom pri plnení vášho sna o vlastnom bývaní.

Visit lexxus.sk

Key Findings

We analyzed Lexxus.sk page load time and found that the first response time was 407 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lexxus.sk performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.179

68/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

lexxus.sk

407 ms

www.lexxus.sk

1365 ms

jquery.fancybox-1.3.1.css

213 ms

style.css

219 ms

galleria.lexxus.css

216 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 19% of them (28 requests) were addressed to the original Lexxus.sk, 27% (40 requests) were made to Zoznamrealit.sk and 22% (32 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Backoffice.sk.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.0 kB (25%)

Content Size

846.0 kB

After Optimization

633.0 kB

In fact, the total size of Lexxus.sk main page is 846.0 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. 60% of websites need less resources to load. Images take 584.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 76.4 kB

  • Original 90.0 kB
  • After minification 64.4 kB
  • After compression 13.6 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 25.6 kB, which is 28% 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 76.4 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 29.5 kB

  • Original 584.5 kB
  • After minification 555.0 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. LEXXUS images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 58.5 kB

  • Original 112.5 kB
  • After minification 85.4 kB
  • After compression 54.0 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 58.5 kB or 52% of the original size.

CSS Optimization

-82%

Potential reduce by 48.6 kB

  • Original 59.0 kB
  • After minification 49.1 kB
  • After compression 10.4 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. Lexxus.sk needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (43%)

Requests Now

109

After Optimization

62

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

Accessibility Review

lexxus.sk accessibility score

60

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

lexxus.sk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lexxus.sk SEO score

91

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SK

  • Language Claimed

    SK

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexxus.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that Lexxus.sk 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 LEXXUS. 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: