Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

puls.no

Musikkavisen Puls

Page Load Speed

6.1 sec in total

First Response

262 ms

Resources Loaded

3.7 sec

Page Rendered

2.2 sec

puls.no screenshot

About Website

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

Musikkavisen Puls. Norges lengstlevende musikkavis.

Visit puls.no

Key Findings

We analyzed Puls.no page load time and found that the first response time was 262 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

puls.no performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

puls.no

262 ms

www.puls.no

1231 ms

KKajax.js

109 ms

puls.js

218 ms

puls2020.css

326 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 70% of them (49 requests) were addressed to the original Puls.no, 7% (5 requests) were made to Pagead2.googlesyndication.com and 7% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Puls.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.7 kB (5%)

Content Size

5.4 MB

After Optimization

5.1 MB

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

HTML Optimization

-70%

Potential reduce by 25.6 kB

  • Original 36.6 kB
  • After minification 36.1 kB
  • After compression 11.0 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 25.6 kB or 70% of the original size.

Image Optimization

-4%

Potential reduce by 197.8 kB

  • Original 4.9 MB
  • After minification 4.7 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. Puls images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 34.4 kB

  • Original 428.3 kB
  • After minification 428.3 kB
  • After compression 393.9 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.

CSS Optimization

-22%

Potential reduce by 930 B

  • Original 4.2 kB
  • After minification 4.2 kB
  • After compression 3.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. Puls.no needs all CSS files to be minified and compressed as it can save up to 930 B or 22% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

56

The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puls. 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

puls.no accessibility score

97

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

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

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

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puls.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Puls.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 Puls. 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: