6.7 sec in total
373 ms
4.2 sec
2.1 sec
Welcome to sz.de homepage info - get ready to check SZ best content for Germany right away, or after learning these important things about sz.de
Nachrichten aus Deutschland und aller Welt mit Kommentaren und Hintergrundberichten.
Visit sz.deWe analyzed Sz.de page load time and found that the first response time was 373 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sz.de performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value3.8 s
56/100
25%
Value10.3 s
8/100
10%
Value9,800 ms
0/100
30%
Value0
100/100
15%
Value16.7 s
5/100
10%
373 ms
1273 ms
358 ms
165 ms
410 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sz.de, 25% (39 requests) were made to S3.eu-central-1.amazonaws.com and 14% (22 requests) were made to Media-cdn.sueddeutsche.de. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Sueddeutsche.de.
Page size can be reduced by 1.0 MB (57%)
1.8 MB
774.7 kB
In fact, the total size of Sz.de main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 946.3 kB which makes up the majority of the site volume.
Potential reduce by 312.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 53.5 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 312.7 kB or 82% of the original size.
Potential reduce by 48.8 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. Obviously, SZ needs image optimization as it can save up to 48.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 505.0 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 505.0 kB or 53% of the original size.
Potential reduce by 143.9 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. Sz.de needs all CSS files to be minified and compressed as it can save up to 143.9 kB or 79% of the original size.
Number of requests can be reduced by 74 (57%)
129
55
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and as a result speed up the page load time.
sz.de
373 ms
www.sueddeutsche.de
1273 ms
sde-core.css
358 ms
sde-header.css
165 ms
sde-core.js
410 ms
sde-header.min.js
169 ms
ima3.js
7 ms
stats.min.js
167 ms
fc633b685338e694f0d7f66aa7becba5
169 ms
iam.js
194 ms
dc.js
30 ms
5ca97fd6.sz-overview-page.cache.css
5 ms
9aafe0e1.sz-overview-page-desktop.cache.js
6 ms
tracking.js
159 ms
gpt.js
49 ms
21746,21748,21750,21985
140 ms
ftg_iq.min.js
276 ms
adex.js
275 ms
iq.js
424 ms
wolkig-rgb_50x60.png
35 ms
placeholder.png
35 ms
nl-icon.png
173 ms
wolkig_nachts-rgb_50x60.png
33 ms
nebel-rgb_50x60.png
35 ms
heiter-rgb_50x60.png
35 ms
tx.io
352 ms
s
1165 ms
__utm.gif
14 ms
gtm.js
94 ms
pixel
18 ms
pubads_impl_82.js
13 ms
pixel
76 ms
sprite_header.png
67 ms
pixel
70 ms
SZSans-Bold.woff
66 ms
SZSans-CondensedBold.woff
64 ms
SZSans-Regular.woff
66 ms
SZSans-CondensedRegular.woff
64 ms
SZSans-Light.woff
66 ms
ads
101 ms
container.html
37 ms
pixel
54 ms
sharingbar_popup_arrow_sprite.png
34 ms
match-result
26 ms
call.js
145 ms
call.js
382 ms
SZText-Bold.woff
33 ms
SZText-Regular.woff
33 ms
rc
276 ms
match-result
14 ms
default.js
214 ms
SZText-RegularItalic.woff
19 ms
SZText-BoldItalic.woff
20 ms
index.html
881 ms
index.html
882 ms
index.html
878 ms
ads
97 ms
sdk.js
14 ms
SZSans-RegularItalic.woff
14 ms
SZSans-CondensedRegularItalic.woff
14 ms
SZSans-BoldItalic.woff
15 ms
SZSans-CondensedBoldItalic.woff
91 ms
osd.js
90 ms
widgets.js
88 ms
szcommon.www.png
84 ms
image.jpg
68 ms
tx.io
155 ms
ads
92 ms
84 ms
p.min.js
89 ms
624 ms
index.html
686 ms
www.sueddeutsche.de
595 ms
blank.gif
414 ms
xd_arbiter.php
412 ms
xd_arbiter.php
649 ms
657 ms
data
839 ms
505 ms
configuration.json
880 ms
analytics.js
487 ms
api.js
552 ms
homepagefeed
519 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
410 ms
jquery-2.2.0.min.js
188 ms
edge.6.0.0.min.js
155 ms
161 ms
pixel
69 ms
1.gif
126 ms
linkid.js
80 ms
s
267 ms
cm.gif
257 ms
like.php
166 ms
2.gif
217 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
59 ms
collect
124 ms
collect
194 ms
collect
132 ms
collect
132 ms
info.json
294 ms
top_edge.js
177 ms
left_edge.js
141 ms
right_edge.js
142 ms
billboard_edge.js
226 ms
fy8tT2klpgR.js
77 ms
LVx-xkvaJ0b.png
71 ms
collect
52 ms
ads
37 ms
2.gif
196 ms
adex.js
140 ms
adrtxtag.min.js
221 ms
ads
47 ms
top_edge.js
127 ms
left_edge.js
125 ms
right_edge.js
97 ms
ads
68 ms
t.js
121 ms
billboard_edge.js
114 ms
right.jpg
166 ms
logo.png
166 ms
warm-winddicht.png
166 ms
jacke.png
173 ms
die-neue-3-in-1-kombination.png
195 ms
button.jpg
198 ms
weste.png
282 ms
line_right2.png
254 ms
winddicht2.png
289 ms
ads
109 ms
left.jpg
232 ms
logo.png
282 ms
warm-winddicht.png
308 ms
jacke_links.png
395 ms
button.jpg
310 ms
die-neue-3-in-1-kombination.png
317 ms
pulli.png
410 ms
line.png
378 ms
warm.png
403 ms
top.jpg
409 ms
produkt-trageoptionen.png
416 ms
jacke_skizze.png
471 ms
plus_skizze.png
490 ms
weste_skizze.png
570 ms
gleich_skizze.png
571 ms
combi_skizze.png
573 ms
jot
98 ms
1.gif
88 ms
analytic.js
85 ms
88 ms
activeview
34 ms
middle.jpg
508 ms
extra-waerme-text.png
512 ms
activeview
15 ms
2.gif
89 ms
chartbeat.js
77 ms
collect
57 ms
sz.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-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
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.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
sz.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
sz.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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sz.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 Sz.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.
sz.de
Open Graph description is not detected on the main page of SZ. 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: