2.8 sec in total
302 ms
1.9 sec
578 ms
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.noWe analyzed Perigon.no page load time and found that the first response time was 302 ms and then it took 2.5 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.
perigon.no performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value4.5 s
37/100
25%
Value9.7 s
11/100
10%
Value18,610 ms
0/100
30%
Value0.002
100/100
15%
Value24.3 s
0/100
10%
302 ms
397 ms
53 ms
190 ms
107 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 39% of them (18 requests) were addressed to the original Perigon.no, 11% (5 requests) were made to No-cache.hubspot.com and 11% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (397 ms) belongs to the original domain Perigon.no.
Page size can be reduced by 73.6 kB (12%)
632.4 kB
558.7 kB
In fact, the total size of Perigon.no main page is 632.4 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. 60% of websites need less resources to load. Images take 482.9 kB which makes up the majority of the site volume.
Potential reduce by 50.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 6.2 kB, which is 11% 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 50.6 kB or 86% of the original size.
Potential reduce by 9.9 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.
Potential reduce by 61 B
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.
Potential reduce by 13.0 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 13.0 kB or 23% of the original size.
Number of requests can be reduced by 20 (53%)
38
18
The browser has sent 38 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 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
perigon.no
302 ms
www.perigon.no
397 ms
jquery-1.7.1.js
53 ms
stratus-modules-1524165234303.min.css
190 ms
layout.min.css
107 ms
stratus-style-1524165235665.css
214 ms
current.js
69 ms
current.js
105 ms
stratus-main-1524165234115.js
219 ms
project.js
74 ms
project.js
75 ms
3853288.js
125 ms
index.js
94 ms
hotjar-1831874.js
130 ms
088e6512-4426-445d-a1fb-0d6698fb09ad.png
88 ms
perigon_green-1.png
280 ms
css
65 ms
font-awesome.css
124 ms
modules.cbd9768ba80ba0be5b17.js
151 ms
f19f7539-efdb-4084-8104-bd67163c5246.png
128 ms
Ocean_Vanguard.jpg
347 ms
Cement%20moving%20downwards.jpeg
284 ms
Cement%20Support%20Tool_CST_3D.png
287 ms
Perigon%20World%20Map_logos_location.png
313 ms
Total_Logo.png
61 ms
Equinor%20logo.png
286 ms
4faa366b-6181-435a-aaa7-35cf67430085.png
182 ms
2667e3ef-953b-4d1b-8f0f-7cc48d631d14.png
200 ms
d46c6d00-07f3-4028-9e82-1e4352b02d37.png
201 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
171 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
253 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
283 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
283 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
283 ms
98325249
277 ms
fontawesome-webfont.woff
226 ms
collectedforms.js
179 ms
leadflows.js
204 ms
3853288.js
297 ms
3853288.js
299 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
124 ms
479002186-fc45c4c98d4e21dc1af98406a2e9b6f72b90e87746813abf66821acd0c5a2c7a-d.jpg
217 ms
player.js
215 ms
player.css
102 ms
vuid.min.js
211 ms
479002186-fc45c4c98d4e21dc1af98406a2e9b6f72b90e87746813abf66821acd0c5a2c7a-d
99 ms
perigon.no accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
perigon.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
perigon.no SEO score
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
Document uses legible font sizes
EN
EN
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.
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: