Access lauritz.com. Køb og sælg på Nordens største auktionshus Lauritz.com

name

value

score

weighting

FCP (First Contentful Paint)

Value17.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value19.7 s

0/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value1.183

1/100

15%

TTI (Time to Interactive)

Value28.5 s

0/100

10%

www.auktionshuset.com

589 ms

Loading.aspx

282 ms

jquery-1.11.3.min.js

236 ms

jquery.cookie.js

471 ms

jqueryURLParser-2.2.js

487 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that all of those requests were addressed to Lauritz.com and no external sources were called. The less responsive or slowest element that took the longest time to load (589 ms) relates to the external source Auktionshuset.com.

Content Size

49.6 kB

After Optimization

42.9 kB

In fact, the total size of Lauritz.com main page is 49.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 48.0 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 1.0 kB

Original 1.5 kB
After minification 1.5 kB
After compression 543 B

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 1.0 kB or 65% of the original size.

JavaScript Optimization

-12%

Potential reduce by 5.7 kB

Original 48.0 kB
After minification 47.3 kB
After compression 42.4 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 5.7 kB or 12% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

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.

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

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

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

High

Page is blocked from indexing

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lauritz.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lauritz.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

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