3.1 sec in total
576 ms
2.2 sec
391 ms
Visit radfazz.de now to see the best up-to-date Rad Fazz content for Germany and also check out these interesting facts you probably never knew about radfazz.de
Fahrradträger und Fahrradhalter für den PKW Innenraum und Reisemobil von RadFazz. Transportieren Sie einfach, sicher, platzsparend und kostengünstig Ihr Fah
Visit radfazz.deWe analyzed Radfazz.de page load time and found that the first response time was 576 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
radfazz.de performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.3 s
70/100
25%
Value5.9 s
48/100
10%
Value100 ms
98/100
30%
Value0.139
79/100
15%
Value8.0 s
42/100
10%
576 ms
431 ms
322 ms
319 ms
322 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 93% of them (57 requests) were addressed to the original Radfazz.de, 3% (2 requests) were made to Code.jquery.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (929 ms) belongs to the original domain Radfazz.de.
Page size can be reduced by 821.0 kB (59%)
1.4 MB
580.9 kB
In fact, the total size of Radfazz.de main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 645.5 kB which makes up the majority of the site volume.
Potential reduce by 59.9 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 59.9 kB or 84% of the original size.
Potential reduce by 80 B
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. Rad Fazz images are well optimized though.
Potential reduce by 518.6 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 518.6 kB or 80% of the original size.
Potential reduce by 242.5 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. Radfazz.de needs all CSS files to be minified and compressed as it can save up to 242.5 kB or 85% of the original size.
Number of requests can be reduced by 39 (66%)
59
20
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rad Fazz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
radfazz.de
576 ms
bootstrap.css
431 ms
offcanvas-menu.css
322 ms
pnotify.custom.css
319 ms
jquery-slider.css
322 ms
style.css
323 ms
suggest.css
422 ms
priceslider.css
423 ms
jquery-1.11.3.min.js
22 ms
jquery-ui.min.js
33 ms
reveal.js
424 ms
jquery.touch.min.js
422 ms
jquery.backstretch.min.js
421 ms
jquery.dimension.js
543 ms
jquery.offcanvas.js
544 ms
jquery.nivo.slider.pack.js
545 ms
jquery.waitforimages.js
546 ms
jquery.lazy.js
545 ms
jquery.serialize-object.js
547 ms
bootstrap.min.js
628 ms
bootstrap-tabdrop.js
542 ms
bootstrap-slider.js
545 ms
bootstrap-modal.js
545 ms
bootstrap-grid.js
543 ms
bootstrap-toolkit.js
548 ms
bootstrap-select.js
646 ms
bootstrap-hover-dropdown.min.js
640 ms
jtl.evo.js
645 ms
jtl.article.js
645 ms
jtl.basket.js
649 ms
jtl.io.js
651 ms
jtl.gallery.js
744 ms
typeahead.bundle.js
853 ms
photoswipe.js
874 ms
imgViewer.js
746 ms
slick.js
749 ms
spin.js
747 ms
global.js
849 ms
suggest.js
637 ms
jquery.dependClass.js
656 ms
jquery.slider.js
653 ms
jtlshoplogo2.jpg
550 ms
loading.gif
551 ms
wb1.jpg
682 ms
wb11.jpg
750 ms
wb12.jpg
757 ms
wb7.jpg
756 ms
wb9.jpg
884 ms
made-in-germany.jpg
114 ms
brd.gif
614 ms
austria.gif
718 ms
schweiz.gif
755 ms
eu.gif
821 ms
SSL-Verschluesselung.jpg
819 ms
Kauf-auf-Rechnung(1).jpg
826 ms
fontawesome-webfont.woff
929 ms
made-in-germany2.jpg
768 ms
cron_inc.php
882 ms
ga.js
50 ms
background_wolken.jpg
638 ms
__utm.gif
12 ms
radfazz.de accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
radfazz.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
radfazz.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Radfazz.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 Radfazz.de main page’s claimed encoding is iso-8859-1. 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.
radfazz.de
Open Graph description is not detected on the main page of Rad Fazz. 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: