Tools & Wizards About Us
um.no screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

um.no

Umoe Mandal: expert in composite high-speed vessels and components.

Page Load Speed

3.3 sec in total

First Response

301 ms

Resources Loaded

2.6 sec

Page Rendered

413 ms

um.no screenshot

About Website

Click here to check amazing Um content. Otherwise, check out these important facts you probably never knew about um.no

Engineering solutions, intelligent materials and bespoke production facilities for designing and building of composite high-speed vessels and structures.

Visit um.no

Key Findings

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

Performance Metrics

um.no performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

www.um.no

301 ms

24fbdcd0-370b-48bf-90a1-3e35894f0861.js

34 ms

style.min.css

42 ms

fontawesome.min.css

45 ms

app.css

50 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 27% of them (9 requests) were addressed to the original Um.no, 58% (19 requests) were made to D4hqalv1xdrvy.cloudfront.net and 6% (2 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source D4hqalv1xdrvy.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.6 kB (7%)

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-86%

Potential reduce by 74.9 kB

  • Original 87.3 kB
  • After minification 75.8 kB
  • After compression 12.4 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 11.5 kB, which is 13% 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 74.9 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 82.6 kB

  • Original 2.2 MB
  • After minification 2.1 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. Um images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 42.1 kB
  • After minification 42.1 kB
  • After compression 42.1 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 3 (10%)

Requests Now

31

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.um.no

www.um.no

301 ms

24fbdcd0-370b-48bf-90a1-3e35894f0861.js

24fbdcd0-370b-48bf-90a1-3e35894f0861.js

34 ms

style.min.css

style.min.css

42 ms

fontawesome.min.css

fontawesome.min.css

45 ms

app.css

app.css

50 ms

jquery.min.js

jquery.min.js

18 ms

uc.js

uc.js

258 ms

app.js

app.js

90 ms

mt.js

mt.js

57 ms

gtm.js

gtm.js

192 ms

Tom-fidjeland-600x400.jpg

Tom-fidjeland-600x400.jpg

164 ms

logo-umoe-mandal-square.png

logo-umoe-mandal-square.png

159 ms

wavecraft-blue-bg.png

wavecraft-blue-bg.png

159 ms

wavecraft-logo-blue.png

wavecraft-logo-blue.png

159 ms

BAE-Type-26--600x400.jpg

BAE-Type-26--600x400.jpg

164 ms

WAVECRAFT-35_photo_set_2_7-Photo-2-600x400.jpg

WAVECRAFT-35_photo_set_2_7-Photo-2-600x400.jpg

166 ms

DSC_0334-650x400.jpg

DSC_0334-650x400.jpg

172 ms

CJ_011_14.06.2011-1-600x400.jpg

CJ_011_14.06.2011-1-600x400.jpg

168 ms

DSC_0633-600x400.jpg

DSC_0633-600x400.jpg

167 ms

20140120th_-30604-1-600x400.jpg

20140120th_-30604-1-600x400.jpg

783 ms

TTD0869-600x400.jpg

TTD0869-600x400.jpg

169 ms

wavecraft-commander-main-650x400.jpg

wavecraft-commander-main-650x400.jpg

171 ms

Picture1-650x400.jpg

Picture1-650x400.jpg

172 ms

KiwaNA_9001.png

KiwaNA_9001.png

992 ms

joscar-logo.png

joscar-logo.png

172 ms

our-story-main-web-2880x1680-1920x600.jpg

our-story-main-web-2880x1680-1920x600.jpg

944 ms

FF83926-1920x600.jpg

FF83926-1920x600.jpg

869 ms

PIC00026-1280x600.jpg

PIC00026-1280x600.jpg

779 ms

20161123NPS_1183-1920x600.jpg

20161123NPS_1183-1920x600.jpg

882 ms

wavecraft-service-and-support-1920x600.jpg

wavecraft-service-and-support-1920x600.jpg

1477 ms

Skjold-Sea-Trials_Side_22-1920x600.jpg

Skjold-Sea-Trials_Side_22-1920x600.jpg

1510 ms

UMOE_webforside_bilde3-1920x600.jpg

UMOE_webforside_bilde3-1920x600.jpg

1680 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

37 ms

Accessibility Review

um.no accessibility score

84

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

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

um.no SEO score

77

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

um.no

Open Graph data is detected on the main page of Um. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: