Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

aperitif.no

Aperitif.no - Vin, mat, kurs, oppskrifter

Page Load Speed

9.1 sec in total

First Response

533 ms

Resources Loaded

5.5 sec

Page Rendered

3 sec

aperitif.no screenshot

About Website

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

Aperitif.no er Norges største nettsted om mat og drikke med en rekke unike tjenester bygget på høy redaksjonell kompetanse.

Visit aperitif.no

Key Findings

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

Performance Metrics

aperitif.no performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value10,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.257

48/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

aperitif.no

533 ms

www.aperitif.no

454 ms

css

29 ms

bundle.css

503 ms

require.min.js

728 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Aperitif.no, 30% (17 requests) were made to Static.tek.no and 16% (9 requests) were made to Img.gfx.no. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Img.gfx.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 659.6 kB (35%)

Content Size

1.9 MB

After Optimization

1.2 MB

In fact, the total size of Aperitif.no main page is 1.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. 60% of websites need less resources to load. Images take 925.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 133.7 kB

  • Original 152.9 kB
  • After minification 101.0 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 51.9 kB, which is 34% 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 133.7 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 3.4 kB

  • Original 925.2 kB
  • After minification 921.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. Aperitif images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 261.0 kB

  • Original 499.6 kB
  • After minification 479.2 kB
  • After compression 238.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 261.0 kB or 52% of the original size.

CSS Optimization

-85%

Potential reduce by 261.5 kB

  • Original 307.1 kB
  • After minification 255.3 kB
  • After compression 45.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. Aperitif.no needs all CSS files to be minified and compressed as it can save up to 261.5 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

20

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aperitif. 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 as a result speed up the page load time.

Accessibility Review

aperitif.no accessibility score

88

Accessibility Issues

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

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

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.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

aperitif.no SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Aperitif.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 Aperitif.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 data is detected on the main page of Aperitif. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: