Tools & Wizards About Us
eleven.no screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

eleven.no

Skjønnhet online ❤ skjønnhetsprodukter på nettet | eleven.no

Page Load Speed

913 ms in total

First Response

59 ms

Resources Loaded

789 ms

Page Rendered

65 ms

eleven.no screenshot

About Website

Welcome to eleven.no homepage info - get ready to check Eleven best content for Norway right away, or after learning these important things about eleven.no

eleven tilbyr et bredt sortiment innen sminke, parfyme, hudpleie og hårpleie. Vi er en autorisert forhandler av skjønnhetsprodukter. Fri frakt over 249 kr!

Visit eleven.no

Key Findings

We analyzed Eleven.no page load time and found that the first response time was 59 ms and then it took 854 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

eleven.no performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value4,400 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

www.nordicfeel.no

59 ms

entry.css

49 ms

theme.nordicfeel.css

194 ms

helloretail.js

106 ms

api_dynamic.js

439 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Eleven.no, 20% (2 requests) were made to Cdn-eu.dynamicyield.com and 10% (1 request) were made to Nordicfeel.no. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source Cdn-eu.dynamicyield.com.

Page Optimization Overview & Recommendations

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

Content Size

2.9 MB

After Optimization

737.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Eleven.no 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. 15% of websites need less resources to load. HTML takes 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 2.1 MB

  • Original 2.6 MB
  • After minification 2.6 MB
  • After compression 537.2 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 80% of the original size.

JavaScript Optimization

-32%

Potential reduce by 87.9 kB

  • Original 272.8 kB
  • After minification 272.8 kB
  • After compression 184.9 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 87.9 kB or 32% of the original size.

CSS Optimization

-0%

Potential reduce by 32 B

  • Original 15.7 kB
  • After minification 15.7 kB
  • After compression 15.7 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. Eleven.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (75%)

Requests Now

8

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

www.nordicfeel.no

www.nordicfeel.no

59 ms

entry.css

entry.css

49 ms

theme.nordicfeel.css

theme.nordicfeel.css

194 ms

helloretail.js

helloretail.js

106 ms

api_dynamic.js

api_dynamic.js

439 ms

api_static.js

api_static.js

451 ms

uc.js

uc.js

48 ms

index.js

index.js

31 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

25 ms

gtm.js

gtm.js

65 ms

Accessibility Review

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

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

High

[aria-*] attributes are not valid or misspelled

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

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

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Page has valid source maps

SEO Factors

eleven.no SEO score

96

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    NB

  • Encoding

    \

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eleven.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Eleven.no main page’s claimed encoding is \. 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

eleven.no

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