Tools & Wizards About Us
handyz.de screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    54% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

handyz.de

Handyhase.de – Die besten Handy-Schnäppchen im Netz

Page Load Speed

6 sec in total

First Response

924 ms

Resources Loaded

3 sec

Page Rendered

2 sec

handyz.de screenshot

About Website

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

Täglich neu: Die besten Deals & Schnäppchen ✔️ Handy mit Vertrag ✔️ Vertrag ohne Handy ✔️ Redaktionell geprüft

Visit handyz.de

Key Findings

We analyzed Handyz.de page load time and found that the first response time was 924 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

handyz.de performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

www.handyz.de

924 ms

style.css

307 ms

font-awesome.css

210 ms

jquery.min.js

9 ms

default.css

308 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 49% of them (41 requests) were addressed to the original Handyz.de, 14% (12 requests) were made to Facebook.com and 14% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (924 ms) belongs to the original domain Handyz.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.5 kB (34%)

Content Size

1.2 MB

After Optimization

797.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Handyz.de main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 656.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.3 kB

  • Original 107.4 kB
  • After minification 104.1 kB
  • After compression 20.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 87.3 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 21.7 kB

  • Original 656.4 kB
  • After minification 634.7 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. Handy Z images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 210.7 kB

  • Original 336.6 kB
  • After minification 332.6 kB
  • After compression 125.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 210.7 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 82.8 kB

  • Original 99.5 kB
  • After minification 77.0 kB
  • After compression 16.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. Handyz.de needs all CSS files to be minified and compressed as it can save up to 82.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (49%)

Requests Now

83

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.handyz.de

www.handyz.de

924 ms

style.css

style.css

307 ms

font-awesome.css

font-awesome.css

210 ms

jquery.min.js

jquery.min.js

9 ms

default.css

default.css

308 ms

fancybox.css

fancybox.css

218 ms

mediaelementplayer.css

mediaelementplayer.css

320 ms

widgets.css

widgets.css

316 ms

jquery.js

jquery.js

628 ms

jquery-migrate.min.js

jquery-migrate.min.js

389 ms

anti-spam.js

anti-spam.js

412 ms

mediaelement-and-player.js

mediaelement-and-player.js

609 ms

adsbygoogle.js

adsbygoogle.js

13 ms

style.css

style.css

143 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

147 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

212 ms

jquery.ui.accordion.min.js

jquery.ui.accordion.min.js

239 ms

jquery.ui.tabs.min.js

jquery.ui.tabs.min.js

250 ms

custom.js

custom.js

256 ms

form.js

form.js

317 ms

fancybox.js

fancybox.js

344 ms

modernizr.js

modernizr.js

357 ms

validate.js

validate.js

467 ms

jquery.cookie.js

jquery.cookie.js

422 ms

stb_init.js

stb_init.js

433 ms

reset.css

reset.css

435 ms

2c-l.css

2c-l.css

432 ms

base.css

base.css

446 ms

header-gradient.png

header-gradient.png

110 ms

logo.png

logo.png

521 ms

horizontal-sep.png

horizontal-sep.png

335 ms

otelo-allnet-flat-xl-s7.jpg

otelo-allnet-flat-xl-s7.jpg

405 ms

samsung-galaxy-s6-tab-a-klarmobil.jpg

samsung-galaxy-s6-tab-a-klarmobil.jpg

337 ms

telekom-magenta-mobil-s-iphone-6s.jpg

telekom-magenta-mobil-s-iphone-6s.jpg

337 ms

Klarmobil-AllNet-Starter-Vodafone.jpg

Klarmobil-AllNet-Starter-Vodafone.jpg

335 ms

winsim-lte-allnet-flats.jpg

winsim-lte-allnet-flats.jpg

470 ms

samsung-galaxy-s6-blau.jpg

samsung-galaxy-s6-blau.jpg

404 ms

mowotel-smart-basic-galaxy-s6-550x276.jpg

mowotel-smart-basic-galaxy-s6-550x276.jpg

403 ms

Vodafone-DataGo-M-Auszahlung.jpg

Vodafone-DataGo-M-Auszahlung.jpg

403 ms

iPhone-6S-Vodafone-Smart-L.jpg

iPhone-6S-Vodafone-Smart-L.jpg

532 ms

samsung-galaxy-s7-vodafone-smart-l1.jpg

samsung-galaxy-s7-vodafone-smart-l1.jpg

531 ms

all.js

all.js

15 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

501 ms

262 ms

xd_arbiter.php

xd_arbiter.php

35 ms

xd_arbiter.php

xd_arbiter.php

258 ms

newsletter2.jpg

newsletter2.jpg

433 ms

ca-pub-6815977921778237.js

ca-pub-6815977921778237.js

336 ms

zrt_lookup.html

zrt_lookup.html

295 ms

show_ads_impl.js

show_ads_impl.js

206 ms

analytics.js

analytics.js

131 ms

likebox.php

likebox.php

385 ms

ads

ads

420 ms

osd.js

osd.js

51 ms

collect

collect

29 ms

like.php

like.php

96 ms

like.php

like.php

108 ms

like.php

like.php

86 ms

like.php

like.php

99 ms

like.php

like.php

72 ms

like.php

like.php

184 ms

like.php

like.php

180 ms

like.php

like.php

180 ms

like.php

like.php

178 ms

like.php

like.php

176 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

140 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

126 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

12 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

6 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

13 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

29 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

28 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

27 ms

67648_492270394127613_1468290271_n.jpg

67648_492270394127613_1468290271_n.jpg

73 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

43 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

31 ms

14387282989197883264

14387282989197883264

55 ms

abg.js

abg.js

55 ms

m_js_controller.js

m_js_controller.js

68 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

47 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

18 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

12 ms

s

s

19 ms

x_button_blue2.png

x_button_blue2.png

20 ms

Accessibility Review

handyz.de accessibility score

80

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

handyz.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

handyz.de SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

handyz.de

Open Graph data is detected on the main page of Handy Z. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: