Tools & Wizards About Us
quadress.de screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

quadress.de

QUADRESS GmbH – The Marketing Data Provider

Page Load Speed

4.4 sec in total

First Response

365 ms

Resources Loaded

3.4 sec

Page Rendered

633 ms

quadress.de screenshot

About Website

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

Die QUADRESS GmbH kombinert das klassische Offline-Dialogmarketing mit moderner Online-Kommunikation in crossmedialen Multi-Channel-Kampagnen. Es werden sowohl Firmenadressen als auch Endkundenadresse...

Visit quadress.de

Key Findings

We analyzed Quadress.de page load time and found that the first response time was 365 ms and then it took 4.1 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

quadress.de performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

quadress.de

365 ms

www.quadress.de

776 ms

system.base.css

95 ms

system.menus.css

188 ms

system.messages.css

189 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 84% of them (96 requests) were addressed to the original Quadress.de, 4% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (893 ms) belongs to the original domain Quadress.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.0 kB (36%)

Content Size

1.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Quadress.de main page is 1.7 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. 50% of websites need less resources to load. Images take 958.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 40.8 kB

  • Original 50.8 kB
  • After minification 46.0 kB
  • After compression 10.0 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 40.8 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 71.1 kB

  • Original 958.8 kB
  • After minification 887.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. QUADRESS images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 281.8 kB

  • Original 412.2 kB
  • After minification 318.5 kB
  • After compression 130.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 281.8 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 206.2 kB

  • Original 242.6 kB
  • After minification 193.7 kB
  • After compression 36.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. Quadress.de needs all CSS files to be minified and compressed as it can save up to 206.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (66%)

Requests Now

104

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

quadress.de

quadress.de

365 ms

www.quadress.de

www.quadress.de

776 ms

system.base.css

system.base.css

95 ms

system.menus.css

system.menus.css

188 ms

system.messages.css

system.messages.css

189 ms

system.theme.css

system.theme.css

190 ms

jquery.ui.core.min.css

jquery.ui.core.min.css

191 ms

jquery.ui.theme.min.css

jquery.ui.theme.min.css

205 ms

jquery.ui.tabs.min.css

jquery.ui.tabs.min.css

221 ms

jquery.ui.accordion.min.css

jquery.ui.accordion.min.css

283 ms

scroll_to_top.css

scroll_to_top.css

282 ms

colorbox_node.css

colorbox_node.css

281 ms

field.css

field.css

283 ms

node.css

node.css

302 ms

user.css

user.css

329 ms

views.css

views.css

374 ms

ckeditor.css

ckeditor.css

376 ms

colorbox_style.css

colorbox_style.css

374 ms

ctools.css

ctools.css

378 ms

animate.css

animate.css

404 ms

md-slider.css

md-slider.css

438 ms

md-slider-style.css

md-slider-style.css

466 ms

webform.css

webform.css

465 ms

eu_cookie_compliance.css

eu_cookie_compliance.css

467 ms

jquery.sidr.dark.css

jquery.sidr.dark.css

473 ms

main.css

main.css

504 ms

jquery.min.js

jquery.min.js

775 ms

jquery.once.js

jquery.once.js

556 ms

drupal.js

drupal.js

557 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

558 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

568 ms

jquery.effects.core.min.js

jquery.effects.core.min.js

607 ms

jquery.ui.tabs.min.js

jquery.ui.tabs.min.js

649 ms

jquery.ui.accordion.min.js

jquery.ui.accordion.min.js

649 ms

jquery.ui.effect.min.js

jquery.ui.effect.min.js

653 ms

form.js

form.js

665 ms

ajax.js

ajax.js

708 ms

conversion.js

conversion.js

48 ms

count.js

count.js

422 ms

jquery_update.js

jquery_update.js

735 ms

de_VAvWgKBAEsAJdW3ZDXRHNJM9l5xzxYy3gp2f9OVlYxw.js

de_VAvWgKBAEsAJdW3ZDXRHNJM9l5xzxYy3gp2f9OVlYxw.js

661 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

573 ms

colorbox.js

colorbox.js

583 ms

colorbox_style.js

colorbox_style.js

635 ms

colorbox_load.js

colorbox_load.js

657 ms

scroll_to_top.js

scroll_to_top.js

642 ms

jquery.touchwipe.js

jquery.touchwipe.js

633 ms

mdvideobox.js

mdvideobox.js

583 ms

modernizr.js

modernizr.js

612 ms

jquery.easing.js

jquery.easing.js

642 ms

md-slider.js

md-slider.js

660 ms

webform.js

webform.js

638 ms

responsive_menus_sidr.js

responsive_menus_sidr.js

617 ms

jquery.sidr.min.js

jquery.sidr.min.js

584 ms

googleanalytics.js

googleanalytics.js

629 ms

progress.js

progress.js

648 ms

colorbox_node.js

colorbox_node.js

656 ms

my_jquery.js

my_jquery.js

628 ms

eu_cookie_compliance.js

eu_cookie_compliance.js

597 ms

yaml-focusfix.js

yaml-focusfix.js

585 ms

css

css

25 ms

css

css

38 ms

css

css

47 ms

font-awesome.css

font-awesome.css

6 ms

base.css

base.css

605 ms

hlist.css

hlist.css

614 ms

gray-theme.css

gray-theme.css

616 ms

content.css

content.css

620 ms

screen-FULLPAGE-layout.css

screen-FULLPAGE-layout.css

574 ms

landingpage-style.css

landingpage-style.css

587 ms

forms-style.css

forms-style.css

663 ms

print.css

print.css

653 ms

ga.js

ga.js

36 ms

logo_0.png

logo_0.png

113 ms

menu-exp.png

menu-exp.png

131 ms

slider-bett.jpg

slider-bett.jpg

893 ms

slider-alle-text.png

slider-alle-text.png

132 ms

slider-bett-text.png

slider-bett-text.png

130 ms

slider-02-bild.jpg

slider-02-bild.jpg

744 ms

slider-02-text.png

slider-02-text.png

201 ms

slider-spiegel_0.jpg

slider-spiegel_0.jpg

774 ms

slider-spiegel-text.png

slider-spiegel-text.png

257 ms

thumb-quadress-imagebroschuere.jpg

thumb-quadress-imagebroschuere.jpg

257 ms

portfolio-thumb.jpg

portfolio-thumb.jpg

470 ms

logo-9001-2008.jpg

logo-9001-2008.jpg

532 ms

logo-quls.png

logo-quls.png

416 ms

logo-arvato.png

logo-arvato.png

510 ms

logo-telegate.png

logo-telegate.png

563 ms

logo-brandrevier.png

logo-brandrevier.png

602 ms

logo-indima.png

logo-indima.png

626 ms

logo-dieda.png

logo-dieda.png

656 ms

logo-tectum.png

logo-tectum.png

694 ms

logo-3dmedia.png

logo-3dmedia.png

722 ms

logo-intertel.png

logo-intertel.png

751 ms

logo-trebbau.png

logo-trebbau.png

788 ms

logo-abilicom.png

logo-abilicom.png

815 ms

logo-protagon.png

logo-protagon.png

849 ms

logo-marancon.png

logo-marancon.png

843 ms

93 ms

__utm.gif

__utm.gif

39 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

34 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

51 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

51 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

gk5FxslNkTTHtojXrkp-xONSK5BxN3NFS4EJkViHIqo.woff

gk5FxslNkTTHtojXrkp-xONSK5BxN3NFS4EJkViHIqo.woff

51 ms

gk5FxslNkTTHtojXrkp-xF1YPouZEKgzpqZW9wN-3Ek.woff

gk5FxslNkTTHtojXrkp-xF1YPouZEKgzpqZW9wN-3Ek.woff

51 ms

collect

collect

269 ms

254 ms

ctin.php

ctin.php

353 ms

up-arrow.png

up-arrow.png

456 ms

slider-bett.jpg

slider-bett.jpg

475 ms

slider-02-bild.jpg

slider-02-bild.jpg

506 ms

slider-spiegel_0.jpg

slider-spiegel_0.jpg

530 ms

md-arrow.png

md-arrow.png

552 ms

Accessibility Review

quadress.de accessibility score

89

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role] values are not valid

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

Links do not have a discernible name

Best Practices

quadress.de best practices score

85

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

quadress.de SEO score

93

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quadress.de 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 Quadress.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

quadress.de

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