Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

lensit.no

Lensit

Page Load Speed

3.7 sec in total

First Response

354 ms

Resources Loaded

3.2 sec

Page Rendered

175 ms

lensit.no screenshot

About Website

Click here to check amazing Lensit content for Norway. Otherwise, check out these important facts you probably never knew about lensit.no

Prisgaranti og lynrask levering av kontaktlinser. Vi har levert linser på nett i 10 år og leverer ekspress fra vårt lager i Norge. Kjøp optikerens linser hos Lensit.no!

Visit lensit.no

Key Findings

We analyzed Lensit.no page load time and found that the first response time was 354 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster. This domain responded with an error, which can significantly jeopardize Lensit.no rating and web reputation

Performance Metrics

lensit.no performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.254

49/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

lensit.no

354 ms

www.lensit.no

713 ms

all.js

28 ms

MyFontsWebfontsKit.css

680 ms

style2.css

935 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 26% of them (19 requests) were addressed to the original Lensit.no, 39% (28 requests) were made to Static.lensit.no and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.lensit.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 384.5 kB (51%)

Content Size

747.5 kB

After Optimization

363.0 kB

In fact, the total size of Lensit.no main page is 747.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. 40% of websites need less resources to load. Javascripts take 389.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.8 kB

  • Original 41.4 kB
  • After minification 34.4 kB
  • After compression 8.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 7.0 kB, which is 17% 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 32.8 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 33.9 kB

  • Original 260.3 kB
  • After minification 226.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. Obviously, Lensit needs image optimization as it can save up to 33.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 272.0 kB

  • Original 389.7 kB
  • After minification 344.4 kB
  • After compression 117.7 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 272.0 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 45.9 kB

  • Original 56.1 kB
  • After minification 46.8 kB
  • After compression 10.2 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. Lensit.no needs all CSS files to be minified and compressed as it can save up to 45.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (42%)

Requests Now

59

After Optimization

34

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

Accessibility Review

lensit.no accessibility score

78

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

[role]s are not contained by their required parent element

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

lensit.no 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

High

Missing source maps for large first-party JavaScript

SEO Factors

lensit.no SEO score

84

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

    NO

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lensit.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lensit.no main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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