Tools & Wizards About Us
wr.no screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

wr.no

Wikborg Rein – Norway's most international law firm

Page Load Speed

4.3 sec in total

First Response

279 ms

Resources Loaded

1.9 sec

Page Rendered

2.1 sec

wr.no screenshot

About Website

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

Wikborg Rein, a leading global law firm offering full-service expertise to national and international businesses in public and private sectors.

Visit wr.no

Key Findings

We analyzed Wr.no page load time and found that the first response time was 279 ms and then it took 4 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

wr.no performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.418

23/100

15%

TTI (Time to Interactive)

Value8.5 s

37/100

10%

Network Requests Diagram

wr.no

279 ms

www.wr.no

509 ms

en

248 ms

a36f9a247607243d.css

153 ms

046340962d32833d.css

246 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 59% of them (22 requests) were addressed to the original Wr.no, 32% (12 requests) were made to V.imgi.no and 3% (1 request) were made to App-script.monsido.com. The less responsive or slowest element that took the longest time to load (613 ms) belongs to the original domain Wr.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.0 kB (3%)

Content Size

2.9 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-78%

Potential reduce by 74.0 kB

  • Original 95.1 kB
  • After minification 94.9 kB
  • After compression 21.1 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 74.0 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.8 MB
  • After minification 2.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. Wr images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 24 B

  • Original 10.8 kB
  • After minification 10.8 kB
  • After compression 10.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.

Requests Breakdown

Number of requests can be reduced by 14 (48%)

Requests Now

29

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wr.no

wr.no

279 ms

www.wr.no

www.wr.no

509 ms

en

en

248 ms

a36f9a247607243d.css

a36f9a247607243d.css

153 ms

046340962d32833d.css

046340962d32833d.css

246 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

408 ms

monsido-script.js

monsido-script.js

23 ms

webpack-01716851e9f7003a.js

webpack-01716851e9f7003a.js

339 ms

framework-2c0fa632eea9ca9a.js

framework-2c0fa632eea9ca9a.js

519 ms

main-c5b50ca764666762.js

main-c5b50ca764666762.js

510 ms

_app-1fb0f7d86de96998.js

_app-1fb0f7d86de96998.js

524 ms

251-534a902ff89e9dbe.js

251-534a902ff89e9dbe.js

611 ms

425-266470ada0dd85da.js

425-266470ada0dd85da.js

487 ms

29-54b7bd51e9a7dc63.js

29-54b7bd51e9a7dc63.js

516 ms

507-cc093e0e4617aa40.js

507-cc093e0e4617aa40.js

596 ms

index-207b21982bdd200e.js

index-207b21982bdd200e.js

602 ms

_buildManifest.js

_buildManifest.js

613 ms

_ssgManifest.js

_ssgManifest.js

605 ms

7tqzl6ucyq.jpg

7tqzl6ucyq.jpg

33 ms

vlkefclnpp.jpg

vlkefclnpp.jpg

206 ms

clkq4rf3ua.jpg

clkq4rf3ua.jpg

44 ms

ljgzc5de2n.jpg

ljgzc5de2n.jpg

41 ms

7ve5d6snzz.jpg

7ve5d6snzz.jpg

40 ms

vhejeg3z3a.jpg

vhejeg3z3a.jpg

528 ms

d5pyk7uab5.jpg

d5pyk7uab5.jpg

38 ms

82ad6u6yau.jpg

82ad6u6yau.jpg

41 ms

exjcv6gmf2.jpg

exjcv6gmf2.jpg

42 ms

amsb4dyah2.jpg

amsb4dyah2.jpg

44 ms

5upqzjh7jp.jpg

5upqzjh7jp.jpg

213 ms

7zrgcc68dm.jpg

7zrgcc68dm.jpg

218 ms

GTSuperDisplay-Regular.woff

GTSuperDisplay-Regular.woff

414 ms

GTSuperDisplay-Medium.woff

GTSuperDisplay-Medium.woff

513 ms

GTSuperDisplay-Light.woff

GTSuperDisplay-Light.woff

521 ms

GTSuperDisplay-Bold.woff

GTSuperDisplay-Bold.woff

497 ms

GTSuperDisplay-Super.woff

GTSuperDisplay-Super.woff

545 ms

heatmaps.js

heatmaps.js

56 ms

page-correct.js

page-correct.js

49 ms

Accessibility Review

wr.no accessibility score

83

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

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

Links do not have a discernible name

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

Best Practices

wr.no best practices score

92

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

SEO Factors

wr.no SEO score

82

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

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

wr.no

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