Tools & Wizards About Us
leki.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

leki.com

LEKI | Stöcke und Handschuhe online kaufen | LEKI

Page Load Speed

2.2 sec in total

First Response

188 ms

Resources Loaded

1.6 sec

Page Rendered

363 ms

leki.com screenshot

About Website

Visit leki.com now to see the best up-to-date LEKI content for Austria and also check out these interesting facts you probably never knew about leki.com

Die besten LEKI Stöcke und Handschuhe für dein Bergabenteuer. Höchste Qualität für Top-Performance. Entwickelt in Deutschland.

Visit leki.com

Key Findings

We analyzed Leki.com page load time and found that the first response time was 188 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

leki.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

leki.com

188 ms

www.leki.com

363 ms

de

475 ms

all.css

480 ms

api.js

31 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 57% of them (8 requests) were addressed to the original Leki.com, 21% (3 requests) were made to Google-analytics.com and 7% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (480 ms) belongs to the original domain Leki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (75%)

Content Size

2.9 MB

After Optimization

716.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Leki.com main page is 2.9 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. 20% of websites need less resources to load. HTML takes 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 2.1 MB

  • Original 2.3 MB
  • After minification 2.2 MB
  • After compression 204.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 2.1 MB or 91% of the original size.

JavaScript Optimization

-0%

Potential reduce by 87 B

  • Original 421.2 kB
  • After minification 421.2 kB
  • After compression 421.1 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 152 B

  • Original 90.8 kB
  • After minification 90.8 kB
  • After compression 90.6 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. Leki.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

leki.com

leki.com

188 ms

www.leki.com

www.leki.com

363 ms

de

de

475 ms

all.css

all.css

480 ms

api.js

api.js

31 ms

all.js

all.js

192 ms

gtm.js

gtm.js

180 ms

logo.svg

logo.svg

203 ms

obvia-book.woff

obvia-book.woff

87 ms

obvia-thin.woff

obvia-thin.woff

97 ms

obvia-medium.woff

obvia-medium.woff

174 ms

analytics.js

analytics.js

50 ms

ec.js

ec.js

6 ms

collect

collect

13 ms

Accessibility Review

leki.com accessibility score

63

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

leki.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

leki.com SEO score

84

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

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

    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 Leki.com 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 Leki.com 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

leki.com

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