6.1 sec in total
418 ms
4.9 sec
826 ms
Click here to check amazing Taz content for Germany. Otherwise, check out these important facts you probably never knew about taz.de
Kritischer, unabhängiger Journalismus der linken Nachrichtenseite taz: Analysen, Hintergründe, Kommentare, Interviews, Reportagen. Genossenschaft seit 1992.
Visit taz.deWe analyzed Taz.de page load time and found that the first response time was 418 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
taz.de performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value10.3 s
0/100
25%
Value13.6 s
2/100
10%
Value19,720 ms
0/100
30%
Value0
100/100
15%
Value29.5 s
0/100
10%
418 ms
302 ms
517 ms
422 ms
123 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 89% of them (98 requests) were addressed to the original Taz.de, 3% (3 requests) were made to Button.flattr.com and 2% (2 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Taz.de.
Page size can be reduced by 1.6 MB (18%)
8.5 MB
6.9 MB
In fact, the total size of Taz.de main page is 8.5 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. 65% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 84.3 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 84.3 kB or 76% of the original size.
Potential reduce by 409.4 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. Taz images are well optimized though.
Potential reduce by 456.1 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 456.1 kB or 68% of the original size.
Potential reduce by 623.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. Taz.de needs all CSS files to be minified and compressed as it can save up to 623.4 kB or 84% of the original size.
Number of requests can be reduced by 22 (23%)
97
75
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Taz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
taz.de
418 ms
news2016-02-23_01.css
302 ms
2016-01-07_01.js
517 ms
iam.js
422 ms
jquery.qtip.min.css
123 ms
535672755_640.jpg
30 ms
redArrowsRight.png
108 ms
baustelle.jpeg
107 ms
14964300.jpeg
233 ms
15375204.jpeg
231 ms
15415295.jpeg
232 ms
imago63970533h.jpeg
231 ms
36174901.jpeg
311 ms
15412861.jpeg
234 ms
imago60681948h.jpg
308 ms
seite1.jpg
405 ms
Mobile-World-Congress-Reuters.jpeg
309 ms
9568845.jpeg
311 ms
kari_preview.jpg
1419 ms
tom_preview.jpg
411 ms
15223381.jpeg
413 ms
15405139.jpeg
416 ms
imago65774360h.jpeg
417 ms
zeozwei-widerstand.jpg
607 ms
little_sun_600x300.jpg
515 ms
Frauentaz_08032016_2-1.png
716 ms
66270700.jpeg
719 ms
15405139.jpeg
513 ms
15235369.jpg
616 ms
Plakat_4.jpeg
717 ms
wahlomat-baden-wuerttemberg_3-2_start.jpg
710 ms
ttip_stoppen_28022016.jpeg
1020 ms
15223381.jpeg
813 ms
Webcam_4-1_mit_Icon_neu.png
1220 ms
15122969.jpeg
820 ms
syrien_produkte1280x640_2016.jpg
822 ms
1497608.jpeg
1015 ms
260515_Schwerpunkt_Fluechtlinge.jpg
1027 ms
15337043.jpeg
922 ms
Bad_Langensalza_Flucht_1_teaser.jpg
1125 ms
Nadja_Tolokonnikowa_dpa_13012016_ccxi.jpeg
1319 ms
549394791_640.jpg
24 ms
tx.io
223 ms
0318.jpeg
1121 ms
fireplace.php
1031 ms
Taz_5_.woff
1252 ms
load.js
9 ms
tx.io
97 ms
Taz_4_.woff
1106 ms
Quodana.ttf
1008 ms
QuodanaB.ttf
1193 ms
Taz_7_.woff
1312 ms
DroidSerif-Regular-webfont.woff
1597 ms
loader.js
10 ms
242 ms
312 ms
Taz_8_.woff
1236 ms
Taz_6_.woff
1235 ms
Taz_4_italic.woff
1213 ms
tree.xml
1328 ms
c.xml
1224 ms
c.xml
1463 ms
c.xml
1447 ms
c.xml
1529 ms
c.xml
1428 ms
button.css
804 ms
button.js
681 ms
c.xml
2224 ms
c.xml
2248 ms
c.xml
1428 ms
c.xml
1437 ms
Wein_1zu1_01.png
1985 ms
Kretschmann_1zu1.png
1532 ms
gefussball_640x640.png
1422 ms
woend_tazzen1280_01.jpg
1435 ms
15408469.jpeg
1430 ms
mueller_holly.jpeg
1438 ms
6187540.jpeg
1521 ms
tzlb_USAEU_achterbahn_HenrikJosefBoerger-dpa.jpg
1729 ms
Auswahl_Sonntaz_300dpi_7-624x312_01.jpg
1345 ms
Bohnen_emoji___photocase.de.jpg
1428 ms
66202148.jpeg
1536 ms
Oscars-Reuters-ZweiEins.jpg
1424 ms
countergif
1528 ms
headerVerlauf.png
1532 ms
tazde.png
1556 ms
tazze64.png
1536 ms
searchShadow.png
1455 ms
vertRedGrad100.png
1439 ms
smallWhArrowR.png
1446 ms
tazze15w.png
1425 ms
paperFoldShadow.png
1416 ms
tazze_dept.png
1321 ms
redUpArrow2.png
1331 ms
redDownArrow2.png
1359 ms
bigWhArrowLeft.png
1357 ms
tazze_dept_w.png
1308 ms
icon_video_small.png
1301 ms
tazde63.png
1121 ms
redDownArrow.png
1102 ms
blocked.gif
1117 ms
faden_aufklapper_f9f9f9.jpg
1137 ms
15412861.jpeg
1075 ms
36174901.jpeg
1215 ms
15375204.jpeg
1007 ms
14964300.jpeg
939 ms
66202148.jpeg
1152 ms
blank.gif
154 ms
print.css
105 ms
a.js
607 ms
taz.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
[role] values are not valid
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
[id] attributes on active, focusable elements are not unique
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
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
taz.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taz.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 Taz.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.
taz.de
Open Graph description is not detected on the main page of Taz. 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: