4.6 sec in total
303 ms
3.9 sec
397 ms
Welcome to viscaal.de homepage info - get ready to check Viscaal best content for Switzerland right away, or after learning these important things about viscaal.de
Ihr zuverlässiger Auto Großhandel für Händler - mit vielen EU-Neuwagen und Reimporten verschiedener Marken, die wir ständig auf Lager haben.
Visit viscaal.deWe analyzed Viscaal.de page load time and found that the first response time was 303 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
viscaal.de performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value6.0 s
13/100
25%
Value7.6 s
26/100
10%
Value1,310 ms
18/100
30%
Value0.204
61/100
15%
Value12.1 s
16/100
10%
303 ms
535 ms
193 ms
205 ms
207 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 59% of them (47 requests) were addressed to the original Viscaal.de, 25% (20 requests) were made to Dms.audaris.de and 3% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Viscaal.de.
Page size can be reduced by 232.4 kB (21%)
1.1 MB
897.8 kB
In fact, the total size of Viscaal.de main page is 1.1 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 892.6 kB which makes up the majority of the site volume.
Potential reduce by 66.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. This page needs HTML code to be minified as it can gain 11.1 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.7 kB or 85% of the original size.
Potential reduce by 46.6 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. Viscaal images are well optimized though.
Potential reduce by 5.5 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 5.5 kB or 23% of the original size.
Potential reduce by 113.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. Viscaal.de needs all CSS files to be minified and compressed as it can save up to 113.5 kB or 84% of the original size.
Number of requests can be reduced by 14 (19%)
73
59
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viscaal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
viscaal.de
303 ms
www.viscaal.de
535 ms
universal.css
193 ms
layout.css
205 ms
customer_febe.css
207 ms
news_home_v3.css
211 ms
home.css
209 ms
home_carscroller.css
211 ms
colorbox.css
399 ms
jquery-ui-1.8.14.custom.css
409 ms
global.css
414 ms
viscaal.de
834 ms
news_home_v3.js
416 ms
home.js
418 ms
home_carscroller.js
603 ms
font-awesome.min.css
6 ms
css
25 ms
all.js
269 ms
ga.js
46 ms
ueb_1473_16137046_1.jpg
308 ms
ueb_1473_15137015_1.jpg
309 ms
ueb_1473_15338508_1.jpg
310 ms
ueb_1473_16117018_1.jpg
312 ms
ueb_1473_16118010_1.jpg
313 ms
ueb_1473_16221005_1.jpg
376 ms
ueb_1473_16221020_1.jpg
517 ms
ueb_1473_16312012_1.jpg
518 ms
ueb_1473_16453520_1.jpg
519 ms
ueb_1473_16457004_1.jpg
527 ms
ueb_1473_16459013_1.jpg
533 ms
ueb_1473_16462008_1.jpg
600 ms
ueb_1473_16632041_1.jpg
721 ms
ueb_1473_16725042_1.jpg
723 ms
ueb_1473_16730501_1.jpg
728 ms
ueb_1473_16731503_1.jpg
735 ms
ueb_1473_16753001_1.jpg
744 ms
ueb_1473_16917508_1.jpg
810 ms
ueb_1473_16973017_1.jpg
927 ms
ueb_1473_16975146_1.jpg
947 ms
7818.
219 ms
logo_1.png
306 ms
navigation.png
207 ms
mainmenu_separator.png
209 ms
arrows.png
211 ms
favorite.png
284 ms
10901_home.png
1138 ms
search.background.png
444 ms
10938.png
454 ms
10939.png
470 ms
10940.png
487 ms
10941.png
504 ms
Grafik_Emblem_Fahrzeugmarken_Audi.png
645 ms
Grafik_Emblem_Fahrzeugmarken_Ford.png
658 ms
Grafik_Emblem_Fahrzeugmarken_Hyundai.png
679 ms
Grafik_Emblem_Fahrzeugmarken_Jeep.png
704 ms
Grafik_Emblem_Fahrzeugmarken_Kia.png
702 ms
Grafik_Emblem_Fahrzeugmarken_Nissan.png
854 ms
Grafik_Emblem_Fahrzeugmarken_Seat.png
853 ms
Grafik_Emblem_Fahrzeugmarken_Skoda.png
881 ms
Grafik_Emblem_Fahrzeugmarken_Suzuki.png
908 ms
Grafik_Emblem_Fahrzeugmarken_VW.png
1014 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
51 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
51 ms
fontawesome-webfont.woff
48 ms
__utm.gif
44 ms
scroll_element_bg.png
983 ms
1pxImages.png
1051 ms
9865.png
1025 ms
9866.png
1057 ms
9867.png
1163 ms
9868.png
1174 ms
9869.png
1233 ms
logo_footer.png
1250 ms
overlay.png
1224 ms
10969_full.jpg
2069 ms
collect
66 ms
166 ms
xd_arbiter.php
212 ms
xd_arbiter.php
423 ms
viscaal.de accessibility score
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
[role]s do not have all required [aria-*] attributes
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
Document doesn't have a <title> element
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
viscaal.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
viscaal.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viscaal.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 Viscaal.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.
viscaal.de
Open Graph description is not detected on the main page of Viscaal. 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: