Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

pixie.nl

Pixie - Voor de sportieve vrouw - Fitness, Lifestyle, Mode, Gezondheid en meer

Page Load Speed

5.2 sec in total

First Response

945 ms

Resources Loaded

4 sec

Page Rendered

241 ms

pixie.nl screenshot

About Website

Click here to check amazing Pixie content. Otherwise, check out these important facts you probably never knew about pixie.nl

Voor de sportieve vrouw - Fitness, Lifestyle, Mode, Gezondheid en meer

Visit pixie.nl

Key Findings

We analyzed Pixie.nl page load time and found that the first response time was 945 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

pixie.nl performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

www.pixie.nl

945 ms

jquery.min.js

35 ms

9a3fcf1b56f77efdec48c5a097d83b49.css

653 ms

prototype.js

811 ms

ccard.js

182 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 79% of them (49 requests) were addressed to the original Pixie.nl, 5% (3 requests) were made to Staticxx.facebook.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pixie.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 946.2 kB (17%)

Content Size

5.6 MB

After Optimization

4.6 MB

In fact, the total size of Pixie.nl main page is 5.6 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. 55% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 37.7 kB

  • Original 49.3 kB
  • After minification 47.7 kB
  • After compression 11.5 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 37.7 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 154.2 kB

  • Original 4.5 MB
  • After minification 4.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. Pixie images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 566.3 kB

  • Original 813.1 kB
  • After minification 694.4 kB
  • After compression 246.8 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 566.3 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 188.0 kB

  • Original 220.6 kB
  • After minification 173.5 kB
  • After compression 32.6 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. Pixie.nl needs all CSS files to be minified and compressed as it can save up to 188.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (40%)

Requests Now

60

After Optimization

36

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

Accessibility Review

pixie.nl accessibility score

68

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

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

pixie.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

pixie.nl SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pixie.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Dutch. Our system also found out that Pixie.nl 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 Pixie. 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: