Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

p4.no

P4 Norge | Lyden av Norge

Page Load Speed

1.5 sec in total

First Response

8 ms

Resources Loaded

1.1 sec

Page Rendered

376 ms

p4.no screenshot

About Website

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

P4 er hele Norges favorittkanal, der kjente programledere som Bjørn Faarlund, Elisabeth Carew, Michael Andreassen, Atle Antonsen og Johan Golden gir deg den beste underholdningen. Du får en god blandi...

Visit p4.no

Key Findings

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

Performance Metrics

p4.no performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,440 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

p4.no

8 ms

p4.no

14 ms

www.p4.no

23 ms

OtAutoBlock.js

60 ms

otSDKStub.js

69 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 48% of them (14 requests) were addressed to the original P4.no, 34% (10 requests) were made to Ddjh0q34m0xak.cloudfront.net and 10% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (920 ms) relates to the external source Ddjh0q34m0xak.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.3 kB (22%)

Content Size

1.1 MB

After Optimization

834.5 kB

In fact, the total size of P4.no main page is 1.1 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. 25% of websites need less resources to load. Images take 813.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 189.4 kB

  • Original 232.3 kB
  • After minification 231.9 kB
  • After compression 42.9 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 189.4 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 36.0 kB

  • Original 813.3 kB
  • After minification 777.3 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. P4 images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 7.9 kB

  • Original 22.2 kB
  • After minification 18.5 kB
  • After compression 14.3 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.9 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (46%)

Requests Now

26

After Optimization

14

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

Accessibility Review

p4.no accessibility score

96

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.

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

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

Missing source maps for large first-party JavaScript

SEO Factors

p4.no SEO score

92

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NB

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise P4.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed language. Our system also found out that P4.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 data is detected on the main page of P4. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: