Tools & Wizards About Us
prizewize.de screenshot

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
    35% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

prizewize.de

Home - Zephyr

Page Load Speed

3.5 sec in total

First Response

372 ms

Resources Loaded

2.9 sec

Page Rendered

229 ms

prizewize.de screenshot

About Website

Visit prizewize.de now to see the best up-to-date Prizewize content and also check out these interesting facts you probably never knew about prizewize.de

Zephyr investeert. En niet alleen financieel. Als ondernemers en informele investeerders hebben we daar al jaren ervaring mee.

Visit prizewize.de

Key Findings

We analyzed Prizewize.de page load time and found that the first response time was 372 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

prizewize.de 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.7 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

prizewize.de

372 ms

www.pricewise.de

606 ms

Gy3PBDIb2P3qtDbisllE3AfzK2GUF_U_GLZZ4gx0vm0_.css

523 ms

2FA9JcJZdcddY3SMwGcibmkGmY6Cu4rKgmWCEI5LX7U_.css

348 ms

WebResource.axd

177 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Prizewize.de, 86% (51 requests) were made to Pricewise.de and 3% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source Pricewise.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (63%)

Content Size

1.9 MB

After Optimization

684.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prizewize.de main page is 1.9 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. 35% of websites need less resources to load. Javascripts take 695.3 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 46.7 kB

  • Original 69.7 kB
  • After minification 66.3 kB
  • After compression 23.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. 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 46.7 kB or 67% of the original size.

Image Optimization

-10%

Potential reduce by 47.9 kB

  • Original 471.0 kB
  • After minification 423.1 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. Prizewize images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 536.7 kB

  • Original 695.3 kB
  • After minification 532.7 kB
  • After compression 158.7 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 536.7 kB or 77% of the original size.

CSS Optimization

-87%

Potential reduce by 545.3 kB

  • Original 624.9 kB
  • After minification 477.4 kB
  • After compression 79.7 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. Prizewize.de needs all CSS files to be minified and compressed as it can save up to 545.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (26%)

Requests Now

57

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prizewize.de

prizewize.de

372 ms

www.pricewise.de

www.pricewise.de

606 ms

Gy3PBDIb2P3qtDbisllE3AfzK2GUF_U_GLZZ4gx0vm0_.css

Gy3PBDIb2P3qtDbisllE3AfzK2GUF_U_GLZZ4gx0vm0_.css

523 ms

2FA9JcJZdcddY3SMwGcibmkGmY6Cu4rKgmWCEI5LX7U_.css

2FA9JcJZdcddY3SMwGcibmkGmY6Cu4rKgmWCEI5LX7U_.css

348 ms

WebResource.axd

WebResource.axd

177 ms

jquery-ui-1.8.15.custom.css

jquery-ui-1.8.15.custom.css

261 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

46 ms

jquery-ui.min.js

jquery-ui.min.js

59 ms

General.js

General.js

599 ms

wz_tooltip.js

wz_tooltip.js

257 ms

WebForms.js

WebForms.js

118 ms

WebUIValidation.js

WebUIValidation.js

143 ms

ScriptResource.axd

ScriptResource.axd

308 ms

ScriptResource.axd

ScriptResource.axd

188 ms

www.pricewise.de

www.pricewise.de

268 ms

energy-start-de.js

energy-start-de.js

264 ms

getseal

getseal

93 ms

currentday.js

currentday.js

263 ms

googleSearchAdd.js

googleSearchAdd.js

483 ms

icon-alert.png

icon-alert.png

92 ms

dritthoechste.png

dritthoechste.png

349 ms

oeko-strom-klein.png

oeko-strom-klein.png

261 ms

pixel-trans.gif

pixel-trans.gif

93 ms

facebook_logo_footer-new.png

facebook_logo_footer-new.png

93 ms

Twitter_Logo_footer-new.png

Twitter_Logo_footer-new.png

93 ms

googleplus_footer-new.png

googleplus_footer-new.png

176 ms

progress_rotating_arrow.gif

progress_rotating_arrow.gif

176 ms

close.png

close.png

174 ms

steps-header-overlay-new.png

steps-header-overlay-new.png

147 ms

mainimage-new.png

mainimage-new.png

842 ms

sc-main-img-overlay.png

sc-main-img-overlay.png

234 ms

steps-header-overlay-new-arrow.png

steps-header-overlay-new-arrow.png

234 ms

gusage1_new.png

gusage1_new.png

218 ms

gusage2_new.png

gusage2_new.png

299 ms

gusage3_new.png

gusage3_new.png

302 ms

gusage4_new.png

gusage4_new.png

306 ms

form-input-bg.gif

form-input-bg.gif

305 ms

icon-info.png

icon-info.png

386 ms

big-green-left-bg_new.png

big-green-left-bg_new.png

387 ms

big-green-bg_new.png

big-green-bg_new.png

388 ms

gas-in-kurze.png

gas-in-kurze.png

471 ms

market-tab.png

market-tab.png

386 ms

market-tab-inactive.png

market-tab-inactive.png

467 ms

hld3-l.png

hld3-l.png

449 ms

hld3-r.png

hld3-r.png

451 ms

hr-bg.gif

hr-bg.gif

456 ms

hld3-corners.png

hld3-corners.png

530 ms

green-check-new.png

green-check-new.png

531 ms

white_purplestroke_withlines.png

white_purplestroke_withlines.png

532 ms

unabhangig.png

unabhangig.png

533 ms

datenschutz.png

datenschutz.png

535 ms

tp_badge-220.png

tp_badge-220.png

21 ms

header-new.png

header-new.png

610 ms

logo-new.png

logo-new.png

610 ms

footer-new.png

footer-new.png

598 ms

footer-new-arrow.png

footer-new-arrow.png

599 ms

progess-trans.png

progess-trans.png

600 ms

gusage3_selected_new.png

gusage3_selected_new.png

644 ms

small-logo.png

small-logo.png

84 ms

Accessibility Review

prizewize.de 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

prizewize.de 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

prizewize.de 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

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prizewize.de can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prizewize.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

prizewize.de

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