Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

2.8 sec in total

First Response

332 ms

Resources Loaded

2.2 sec

Page Rendered

259 ms

pricerunner.de screenshot

About Website

Welcome to pricerunner.de homepage info - get ready to check Pricerunner best content for Germany right away, or after learning these important things about pricerunner.de

Vergleichen sie Preise für Produkte aus vielen Kategorien. Preisvergleich und Nutzer- und Expertenmeinungen helfen das beste Produkt zum besten Preis zu finden.

Visit pricerunner.de

Key Findings

We analyzed Pricerunner.de page load time and found that the first response time was 332 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

pricerunner.de performance score

0

Network Requests Diagram

www.pricerunner.de

332 ms

core.css

16 ms

override_de.css

107 ms

core.js

36 ms

conversion.js

87 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pricerunner.de, 63% (56 requests) were made to Images.pricerunner.com and 11% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (801 ms) relates to the external source Images.pricerunner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 984.3 kB (66%)

Content Size

1.5 MB

After Optimization

502.1 kB

In fact, the total size of Pricerunner.de 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. 45% of websites need less resources to load. Images take 817.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 64.2 kB

  • Original 77.3 kB
  • After minification 65.3 kB
  • After compression 13.1 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 12.0 kB, which is 15% 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 64.2 kB or 83% of the original size.

Image Optimization

-58%

Potential reduce by 476.1 kB

  • Original 817.7 kB
  • After minification 341.6 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. Obviously, Pricerunner needs image optimization as it can save up to 476.1 kB or 58% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 102.7 kB

  • Original 193.0 kB
  • After minification 192.9 kB
  • After compression 90.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 102.7 kB or 53% of the original size.

CSS Optimization

-86%

Potential reduce by 341.3 kB

  • Original 398.4 kB
  • After minification 366.7 kB
  • After compression 57.0 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. Pricerunner.de needs all CSS files to be minified and compressed as it can save up to 341.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (31%)

Requests Now

87

After Optimization

60

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

SEO Factors

pricerunner.de SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    DE

  • Encoding

    UTF-8

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