Tools & Wizards About Us
handysuche.net screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

handysuche.net

Handy-Suche und Handy-Vergleich zu aktuellen Handys, PDAs und Smartphones

Page Load Speed

1.7 sec in total

First Response

225 ms

Resources Loaded

1.3 sec

Page Rendered

115 ms

handysuche.net screenshot

About Website

Click here to check amazing Handy Suche content for Germany. Otherwise, check out these important facts you probably never knew about handysuche.net

Sie suchen nach einen bestimmten Handy oder einer bestimmten Marke? Nutzen Sie unsere kostenlose Handysuchmaschine und den Handy-Vergleich um schnell zu finden, was Sie suchen

Visit handysuche.net

Key Findings

We analyzed Handysuche.net page load time and found that the first response time was 225 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

handysuche.net performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.706

7/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

handysuche.net

225 ms

www.handysuche.net

328 ms

960.css

443 ms

style.css

449 ms

default.css

129 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 83% of them (15 requests) were addressed to the original Handysuche.net, 11% (2 requests) were made to Tariffuxx.de and 6% (1 request) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (555 ms) belongs to the original domain Handysuche.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.6 kB (15%)

Content Size

99.3 kB

After Optimization

84.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Handysuche.net main page is 99.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 74.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 9.6 kB

  • Original 13.3 kB
  • After minification 12.1 kB
  • After compression 3.7 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 9.6 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 1.0 kB

  • Original 74.0 kB
  • After minification 73.0 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 Suche images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 2.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. This website has mostly compressed JavaScripts.

CSS Optimization

-42%

Potential reduce by 3.9 kB

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 5.4 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. Handysuche.net needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 42% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

12

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

handysuche.net

handysuche.net

225 ms

www.handysuche.net

www.handysuche.net

328 ms

960.css

960.css

443 ms

style.css

style.css

449 ms

default.css

default.css

129 ms

txhandygalery.php

txhandygalery.php

444 ms

logo.png

logo.png

555 ms

mobile

mobile

130 ms

custom.css

custom.css

113 ms

gplus-16.png

gplus-16.png

28 ms

bg.jpg

bg.jpg

103 ms

bg-header.jpg

bg-header.jpg

203 ms

bg-content.png

bg-content.png

206 ms

handyvertrag.jpg

handyvertrag.jpg

205 ms

handyauszahlung.jpg

handyauszahlung.jpg

206 ms

prepaidhandys.jpg

prepaidhandys.jpg

206 ms

handyvergleich.jpg

handyvergleich.jpg

206 ms

category_image_block_bg.jpg

category_image_block_bg.jpg

104 ms

Accessibility Review

handysuche.net accessibility score

65

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

handysuche.net best practices score

67

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

handysuche.net SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Handysuche.net can be misinterpreted by Google and other search engines. Our service has detected that German 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 Handysuche.net main page’s claimed encoding is utf8. 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

handysuche.net

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