Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

pp.dk

PP Møbler - Wegner Chairs & Danish Design Furniture

Page Load Speed

3.4 sec in total

First Response

589 ms

Resources Loaded

2.6 sec

Page Rendered

226 ms

pp.dk screenshot

About Website

Visit pp.dk now to see the best up-to-date PP content for United States and also check out these interesting facts you probably never knew about pp.dk

PP Møbler is Denmark's most respected joinery and cabinet maker workshop producing premium quality furniture. The designer Hans J. Wegner developed many of his most successful chairs working with...

Visit pp.dk

Key Findings

We analyzed Pp.dk page load time and found that the first response time was 589 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pp.dk performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value3,680 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

pp.dk

589 ms

jquery.min.js

31 ms

jquery.cycle.all.min.js

423 ms

pp_top_logo.gif

344 ms

prev.png

227 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 84% of them (16 requests) were addressed to the original Pp.dk, 11% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pp.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.3 kB (2%)

Content Size

2.4 MB

After Optimization

2.3 MB

In fact, the total size of Pp.dk main page is 2.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. 20% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.3 kB

  • Original 28.5 kB
  • After minification 27.9 kB
  • After compression 6.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 22.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 2.3 MB
  • After minification 2.3 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. PP images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 22.6 kB

  • Original 46.7 kB
  • After minification 46.0 kB
  • After compression 24.2 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 22.6 kB or 48% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PP. According to our analytics all requests are already optimized.

Accessibility Review

pp.dk 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pp.dk 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pp.dk SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pp.dk 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 Pp.dk main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of PP. 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: