Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ifpi.no

IFPI – Representing the recording industry worldwide

Page Load Speed

4 sec in total

First Response

903 ms

Resources Loaded

3 sec

Page Rendered

185 ms

ifpi.no screenshot

About Website

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

IFPI Norge er en forening for norske plateselskaper stiftet i 1939. Medlemmer er norske datterselskaper av de fire største internasjonale plateselskapene Universal, Sony, Emi og Warner, samt rent nors...

Visit ifpi.no

Key Findings

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

ifpi.no performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

ifpi.no

903 ms

jquery.js

72 ms

k2.css

66 ms

stylesheet.css

66 ms

css.php

139 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 73% of them (48 requests) were addressed to the original Ifpi.no, 14% (9 requests) were made to Google.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ifpi.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 703.8 kB (47%)

Content Size

1.5 MB

After Optimization

779.1 kB

In fact, the total size of Ifpi.no main page is 1.5 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. Javascripts take 646.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 30.5 kB

  • Original 38.8 kB
  • After minification 34.3 kB
  • After compression 8.3 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 4.5 kB, which is 12% 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 30.5 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 44.1 kB

  • Original 585.4 kB
  • After minification 541.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. IFPI images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 445.6 kB

  • Original 646.0 kB
  • After minification 615.6 kB
  • After compression 200.4 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 445.6 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 183.6 kB

  • Original 212.8 kB
  • After minification 161.5 kB
  • After compression 29.2 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. Ifpi.no needs all CSS files to be minified and compressed as it can save up to 183.6 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

60

After Optimization

14

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IFPI. 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 from 17 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ifpi.no accessibility score

91

Accessibility Issues

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

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

ifpi.no SEO score

92

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

Image elements do not have [alt] attributes

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

    NO

  • Language Claimed

    NB

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifpi.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 Ifpi.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 description is not detected on the main page of IFPI. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: