Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

oleaas.no

Gullsmed Aas - Forlovelsesring, diamanter og gifteringer er våre spesialiteter.

Page Load Speed

11.2 sec in total

First Response

351 ms

Resources Loaded

10.3 sec

Page Rendered

574 ms

oleaas.no screenshot

About Website

Click here to check amazing Ole Aas content. Otherwise, check out these important facts you probably never knew about oleaas.no

Gullsmed Aas etablert i 1874 er spesialister i Forlovelsesring, gifteringer og diamanter. Vi har stort utvalg av Swarovski, dåpsgaver, gullsmykker og gullringer.

Visit oleaas.no

Key Findings

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

Performance Metrics

oleaas.no performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value560 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

oleaas.no

351 ms

oleaas.no

5026 ms

webfont.js

14 ms

eeassolo20oisdzwphrbwvno7vbobwdam4nc5ivafgc1

271 ms

htni9wfigv7q1fixe6nznouxgfrnugljb372ryrrpqa1

852 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 92% of them (73 requests) were addressed to the original Oleaas.no, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Oleaas.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.8 kB (8%)

Content Size

1.7 MB

After Optimization

1.5 MB

In fact, the total size of Oleaas.no main page is 1.7 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. 30% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 91.2 kB

  • Original 106.8 kB
  • After minification 88.9 kB
  • After compression 15.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 17.9 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 91.2 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 47.6 kB

  • Original 1.5 MB
  • After minification 1.5 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. Ole Aas images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 7 (9%)

Requests Now

75

After Optimization

68

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

Accessibility Review

oleaas.no accessibility score

96

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 input fields do not have accessible names

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

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

Page has valid source maps

SEO Factors

oleaas.no SEO score

100

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oleaas.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 Oleaas.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 Ole Aas. 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: