Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

audi.no

Audi Norge | Audi.no

Page Load Speed

2.7 sec in total

First Response

315 ms

Resources Loaded

2.3 sec

Page Rendered

133 ms

audi.no screenshot

About Website

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

Velkommen til Audi Norge. Her får du oversikt over Audis bilmodeller, priser og nyheter. Prøvekjør en av våre modeller og finn drømmebilen din i dag.

Visit audi.no

Key Findings

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

Performance Metrics

audi.no performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value4,240 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

audi.no

315 ms

www.audi.no

471 ms

no.html

16 ms

css.css

79 ms

extension.css

162 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 84% of them (81 requests) were addressed to the original Audi.no, 3% (3 requests) were made to Track.adform.net and 2% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (579 ms) belongs to the original domain Audi.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 881.3 kB (15%)

Content Size

6.0 MB

After Optimization

5.1 MB

In fact, the total size of Audi.no main page is 6.0 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 125.1 kB

  • Original 137.7 kB
  • After minification 123.5 kB
  • After compression 12.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. 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 125.1 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 89.3 kB

  • Original 4.9 MB
  • After minification 4.8 MB

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. Audi images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 409.7 kB

  • Original 644.5 kB
  • After minification 628.0 kB
  • After compression 234.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 409.7 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 257.2 kB

  • Original 305.6 kB
  • After minification 302.3 kB
  • After compression 48.4 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. Audi.no needs all CSS files to be minified and compressed as it can save up to 257.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (22%)

Requests Now

91

After Optimization

71

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

Accessibility Review

audi.no accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

audi.no best practices score

75

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

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

audi.no SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    DE

  • Encoding

    UTF-8

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