5.3 sec in total
419 ms
4.5 sec
347 ms
Welcome to wizo.de homepage info - get ready to check Wizo best content for Germany right away, or after learning these important things about wizo.de
WIZO - Die Legende der 90er - Die antifaschistische Punkrockband aus Sindelfingen - Die mit dem grünen Fert mit der Ölablassschraube - Mit RAUM DER ZEIT, QUADRAT IM KREIS, der SEEGURKE, dem Dackel und...
Visit wizo.deWe analyzed Wizo.de page load time and found that the first response time was 419 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wizo.de performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.2 s
23/100
25%
Value7.4 s
28/100
10%
Value20 ms
100/100
30%
Value0.14
79/100
15%
Value8.0 s
42/100
10%
419 ms
110 ms
204 ms
208 ms
3915 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 30% of them (25 requests) were addressed to the original Wizo.de, 48% (39 requests) were made to Static.xx.fbcdn.net and 21% (17 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Wizo.de.
Page size can be reduced by 190.3 kB (7%)
2.9 MB
2.7 MB
In fact, the total size of Wizo.de main page is 2.9 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. 45% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 8.5 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 1.3 kB, which is 11% 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 8.5 kB or 74% of the original size.
Potential reduce by 176.9 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. Wizo images are well optimized though.
Potential reduce by 1.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 1.6 kB or 70% of the original size.
Potential reduce by 3.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. Wizo.de needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 75% of the original size.
Number of requests can be reduced by 39 (48%)
81
42
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wizo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
wizo.de
419 ms
style.css
110 ms
common_script.js
204 ms
jsScroller.js
208 ms
bg.jpg
3915 ms
bg_main.png
1611 ms
Pgnu_Thumb.jpg
114 ms
rockpalast_thumb.jpg
111 ms
pfingstspektakel_thumb.jpg
208 ms
rockamsee_thumb.jpg
214 ms
highfield_area4_thumb.jpg
212 ms
bach_thumb.jpg
217 ms
mach1_thumb.jpg
309 ms
greenfield_thumb.jpg
314 ms
rodeo_thumb.jpg
319 ms
studio1_thumb.jpg
321 ms
studio2_thumb.jpg
409 ms
merch.jpg
415 ms
playerbox_bg.png
812 ms
videos_bg.png
516 ms
facebook_bg.png
889 ms
newsletter_bg.png
605 ms
termine_bg.png
722 ms
merchbox_bg.png
806 ms
footer.png
827 ms
likebox.php
347 ms
V89xIM8XrVh.css
280 ms
mKIPuHvlbBA.css
348 ms
bVRH4F6MjT7.css
415 ms
uWl49LVNhfl.css
561 ms
3PXshBSsmpj.css
547 ms
eogjeCD83db.css
482 ms
CkBJsJ-mGCK.css
555 ms
XCdv7aD40Gm.js
613 ms
lnwXDK64af8.js
627 ms
mn6tHWuLI-Y.js
570 ms
x8BMxYCqTb9.js
637 ms
QKy94bWvcbp.js
640 ms
5paioeCYCa7.js
638 ms
wRXOQ26LQ1k.js
751 ms
UMeIUxuSxxa.js
816 ms
50Trs1RKgUY.js
680 ms
VAFHT3WOlau.js
685 ms
yThLVep5o7U.js
749 ms
RHOBjz8KA-m.js
683 ms
LIHAaXrKkGk.js
840 ms
In8KOzYgNHs.js
757 ms
K8Vhkfx1wbZ.js
755 ms
Pgc3fKJZhcQ.js
846 ms
xRbzcXUWYBl.js
849 ms
1959591_10152879418915750_5063048944763976010_n.jpg
344 ms
10376306_10152447253275750_6775867044414573071_n.jpg
400 ms
1507888_247887648886935_2517019397649984727_n.jpg
528 ms
12806002_137664826623246_8306335485845890001_n.jpg
533 ms
12729064_1699761503642712_3703895581287171430_n.jpg
593 ms
12321503_243685002646642_3405540177892444206_n.jpg
604 ms
10462963_816101561816923_1609436675343446343_n.jpg
532 ms
12376688_1125778620777456_6958371522462002201_n.jpg
744 ms
12565469_1751221981776001_4045345604552327030_n.jpg
594 ms
6784_205397069832033_2196269723732743223_n.jpg
623 ms
11152683_648946148572602_552173677366134990_n.jpg
672 ms
1555435_1630016070566284_390521583940508832_n.jpg
719 ms
10453454_964968850205760_6031436532864202882_n.png
1129 ms
12672338_496044643911973_590337898_n.jpg
737 ms
12514157_10154285506791030_1889392764_n.jpg
758 ms
1013326_10153828737026974_9051889879423115197_n.jpg
804 ms
12243350_10154619916329815_6151000814944411140_n.png
1123 ms
wL6VQj7Ab77.png
72 ms
s7jcwEQH7Sx.png
73 ms
mbF8ssTVP_5.png
73 ms
Fe6g47SXw-8.png
73 ms
L5AOQ9vzKfo.png
75 ms
oULnqcel5Nm.png
74 ms
q2ibvFgTxmh.png
136 ms
A2JLtDOGyCJ.png
134 ms
pimRBh7B6ER.png
136 ms
l5aPruN9xMM.png
136 ms
Db1xvLoJ2np.png
139 ms
Fy3hs8lKW0M.png
137 ms
S4NGepoqhZB.js
152 ms
tTcfgDp1_5_.png
132 ms
VXcANLwwL5J.js
68 ms
wizo.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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
wizo.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wizo.de SEO score
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
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wizo.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wizo.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.
wizo.de
Open Graph description is not detected on the main page of Wizo. 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: