Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

scanholm.no

Foodstuff.no - kvalitetsprodukter til røyking, grilling og lagring av mat

Page Load Speed

4.1 sec in total

First Response

315 ms

Resources Loaded

3.3 sec

Page Rendered

436 ms

scanholm.no screenshot

About Website

Visit scanholm.no now to see the best up-to-date Scanholm content for Norway and also check out these interesting facts you probably never knew about scanholm.no

Hos oss finner du kvalitetsprodukter til røyking, grilling og lagring av mat. Vi har et stort utvalg av ulike typer krydder, smaktilsettninger, samt råvarer og utstyr som trengs for å lage hjemmelagde...

Visit scanholm.no

Key Findings

We analyzed Scanholm.no page load time and found that the first response time was 315 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

scanholm.no performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.093

91/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

scanholm.no

315 ms

www.foodstuff.no

1632 ms

tarteaucitron.css

407 ms

css

59 ms

theme-595c59430.css

415 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Scanholm.no, 44% (22 requests) were made to Foodstuff.no and 24% (12 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Foodstuff.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.2 kB (16%)

Content Size

1.6 MB

After Optimization

1.4 MB

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

HTML Optimization

-89%

Potential reduce by 229.8 kB

  • Original 258.3 kB
  • After minification 206.8 kB
  • After compression 28.5 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 51.5 kB, which is 20% 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 229.8 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 6.4 kB

  • Original 630.3 kB
  • After minification 623.9 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. Scanholm images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 26.6 kB

  • Original 645.4 kB
  • After minification 643.9 kB
  • After compression 618.8 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

-1%

Potential reduce by 1.4 kB

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

Requests Breakdown

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

Requests Now

42

After Optimization

19

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

Accessibility Review

scanholm.no accessibility score

79

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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

scanholm.no best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

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

scanholm.no SEO score

92

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

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