Tools & Wizards About Us
perigon.no screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

perigon.no

Perigon | Cement Support Tool (CST) for off-bottom (balanced) cement plugs

Page Load Speed

2.4 sec in total

First Response

132 ms

Resources Loaded

1.7 sec

Page Rendered

516 ms

perigon.no screenshot

About Website

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

When setting off-bottom (balanced) cement plugs, you want 100 per cent success at first attempt. The Cement Support Tool (CST) is a mechanical base for the cement plug, with a proven industry leading ...

Visit perigon.no

Key Findings

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

Performance Metrics

perigon.no performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.7 s

18/100

10%

Network Requests Diagram

perigon.no

132 ms

www.perigon.no

312 ms

pwr-burger.min.css

163 ms

scroll-shadow.min.css

283 ms

js

72 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 74% of them (31 requests) were addressed to the original Perigon.no, 5% (2 requests) were made to 3853288.fs1.hubspotusercontent-na1.net and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (948 ms) relates to the external source 3853288.fs1.hubspotusercontent-na1.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 457.9 kB (50%)

Content Size

908.5 kB

After Optimization

450.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Perigon.no main page is 908.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 494.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 431.1 kB

  • Original 494.2 kB
  • After minification 487.3 kB
  • After compression 63.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. 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 431.1 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 19.1 kB

  • Original 353.5 kB
  • After minification 334.4 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. Perigon images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 7.4 kB

  • Original 58.0 kB
  • After minification 58.0 kB
  • After compression 50.6 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 7.4 kB or 13% of the original size.

CSS Optimization

-15%

Potential reduce by 412 B

  • Original 2.8 kB
  • After minification 2.8 kB
  • After compression 2.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. Perigon.no needs all CSS files to be minified and compressed as it can save up to 412 B or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (68%)

Requests Now

34

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

perigon.no

perigon.no

132 ms

www.perigon.no

www.perigon.no

312 ms

pwr-burger.min.css

pwr-burger.min.css

163 ms

scroll-shadow.min.css

scroll-shadow.min.css

283 ms

js

js

72 ms

embed.js

embed.js

31 ms

pwr.min.js

pwr.min.js

733 ms

child.min.js

child.min.js

45 ms

project.js

project.js

67 ms

pwr-burger.min.js

pwr-burger.min.js

244 ms

scroll-shadow.min.js

scroll-shadow.min.js

269 ms

pwr-search.min.js

pwr-search.min.js

248 ms

project.js

project.js

192 ms

advanced-mm.min.js

advanced-mm.min.js

428 ms

pwr-grid.min.js

pwr-grid.min.js

504 ms

Waypoints.min.js

Waypoints.min.js

467 ms

CounterUp2.min.js

CounterUp2.min.js

468 ms

pwr-stat.min.js

pwr-stat.min.js

446 ms

_dateformat.min.js

_dateformat.min.js

638 ms

web-interactives-embed.js

web-interactives-embed.js

51 ms

v2.js

v2.js

501 ms

3853288.js

3853288.js

529 ms

index.js

index.js

497 ms

hotjar-1831874.js

hotjar-1831874.js

193 ms

PP%20Bakgrunn.jpg

PP%20Bakgrunn.jpg

668 ms

interactive-170654973968.png

interactive-170654973968.png

220 ms

perigon_green-1.png

perigon_green-1.png

216 ms

perigon_green-1.png

perigon_green-1.png

235 ms

6.jpg

6.jpg

552 ms

linkedin_3536569_icon.png

linkedin_3536569_icon.png

249 ms

4%20closest.jpeg

4%20closest.jpeg

948 ms

500.woff

500.woff

528 ms

regular.woff

regular.woff

401 ms

700.woff

700.woff

357 ms

regular.woff

regular.woff

280 ms

500.woff

500.woff

475 ms

700.woff

700.woff

574 ms

related-blog-posts-callback

related-blog-posts-callback

473 ms

banner.js

banner.js

105 ms

3853288.js

3853288.js

225 ms

fb.js

fb.js

99 ms

collectedforms.js

collectedforms.js

85 ms

Accessibility Review

perigon.no accessibility score

95

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

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

perigon.no

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