Tools & Wizards About Us
lexum.pl screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lexum.pl

Specjalistyczne Kliniki Okulistyczne Optegra - okulista

Page Load Speed

5.2 sec in total

First Response

40 ms

Resources Loaded

4.3 sec

Page Rendered

890 ms

lexum.pl screenshot

About Website

Click here to check amazing Lexum content for Poland. Otherwise, check out these important facts you probably never knew about lexum.pl

Kliniki Optegra powstały z myślą o ludziach borykających się ze schorzeniami narządu wzroku. Zajmujemy się laserową korekcją wzroku, operacjami zaćmy oraz innymi chorobami oczu.

Visit lexum.pl

Key Findings

We analyzed Lexum.pl page load time and found that the first response time was 40 ms and then it took 5.2 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

lexum.pl performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

65/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

lexum.pl

40 ms

www.optegra.com.pl

995 ms

jquery.min.js

370 ms

612d90d4f3cba9e1adff9772a158d3f0.js

290 ms

email-decode.min.js

33 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Lexum.pl, 91% (32 requests) were made to Optegra.com.pl and 3% (1 request) were made to Cdn.thulium.com. The less responsive or slowest element that took the longest time to load (995 ms) relates to the external source Optegra.com.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.5 kB (17%)

Content Size

699.5 kB

After Optimization

583.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lexum.pl main page is 699.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. 25% of websites need less resources to load. Images take 424.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 100.8 kB

  • Original 131.4 kB
  • After minification 131.4 kB
  • After compression 30.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. 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 100.8 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 15.5 kB

  • Original 424.0 kB
  • After minification 408.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. Lexum images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 170 B

  • Original 97.6 kB
  • After minification 97.6 kB
  • After compression 97.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 38 B

  • Original 46.5 kB
  • After minification 46.5 kB
  • After compression 46.5 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. Lexum.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (72%)

Requests Now

32

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lexum.pl

lexum.pl

40 ms

www.optegra.com.pl

www.optegra.com.pl

995 ms

jquery.min.js

jquery.min.js

370 ms

612d90d4f3cba9e1adff9772a158d3f0.js

612d90d4f3cba9e1adff9772a158d3f0.js

290 ms

email-decode.min.js

email-decode.min.js

33 ms

chat-loader.js

chat-loader.js

408 ms

846b487e82f9962462c25e673a2f9a5f.js

846b487e82f9962462c25e673a2f9a5f.js

66 ms

8a8f3e357ad9568aaef820257db4c7d4.js

8a8f3e357ad9568aaef820257db4c7d4.js

406 ms

c4cc3d9f3225a80ce25ed4c6fe11a562.js

c4cc3d9f3225a80ce25ed4c6fe11a562.js

406 ms

739671b87ce677db0adf796cddb35a76.js

739671b87ce677db0adf796cddb35a76.js

406 ms

53eafcf8655ded2b16132437392f4623.js

53eafcf8655ded2b16132437392f4623.js

93 ms

e74f42e97e7cf4114d327281503d1c52.js

e74f42e97e7cf4114d327281503d1c52.js

120 ms

9e50db3100acdd2c474f9d1154b9b415.js

9e50db3100acdd2c474f9d1154b9b415.js

148 ms

15d388acb613832ecd3897b90bd654bd.js

15d388acb613832ecd3897b90bd654bd.js

168 ms

b3cd004fc02709b1806a93b400dcc2f6.js

b3cd004fc02709b1806a93b400dcc2f6.js

187 ms

61a23544de68ae8b67971c715b8e1e09.js

61a23544de68ae8b67971c715b8e1e09.js

209 ms

9dd19fc0fd315b5d3439c39e9aa8dbeb.js

9dd19fc0fd315b5d3439c39e9aa8dbeb.js

227 ms

70892cfa18e2a0a7917cbd217268dee9.js

70892cfa18e2a0a7917cbd217268dee9.js

251 ms

d29ef2d4724b505e689e377c3fd93179.js

d29ef2d4724b505e689e377c3fd93179.js

271 ms

3dd47be43d0e99535e7cdf8feaaafcf4.js

3dd47be43d0e99535e7cdf8feaaafcf4.js

296 ms

gtm.js

gtm.js

153 ms

placeholder.png

placeholder.png

284 ms

logo_optegra_25_lat.svg

logo_optegra_25_lat.svg

287 ms

zeiss2.png

zeiss2.png

359 ms

reserve-ornament.svg

reserve-ornament.svg

275 ms

ornament-3.svg

ornament-3.svg

285 ms

banner_lkw.png

banner_lkw.png

684 ms

banner_lkw_mobile.png

banner_lkw_mobile.png

864 ms

36229b3897ba9eef1650e9b097bcde37.css

36229b3897ba9eef1650e9b097bcde37.css

282 ms

754e472730ae8e11a06bd3bf5079ce0e.css

754e472730ae8e11a06bd3bf5079ce0e.css

16 ms

e8c7fd6e257d386e9696a067d5774a5e.css

e8c7fd6e257d386e9696a067d5774a5e.css

361 ms

ae33b102bda91fd84ecae91cee1ead57.css

ae33b102bda91fd84ecae91cee1ead57.css

276 ms

eb1e2b62f4724bf164c045d9cbe41483.css

eb1e2b62f4724bf164c045d9cbe41483.css

355 ms

b6057065eecd83fa4e49701789ae1df2.css

b6057065eecd83fa4e49701789ae1df2.css

273 ms

optegra.ttf

optegra.ttf

278 ms

Accessibility Review

lexum.pl accessibility score

77

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

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

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

lexum.pl 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lexum.pl SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

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

lexum.pl

Open Graph data is detected on the main page of Lexum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: