4.4 sec in total
251 ms
3.4 sec
734 ms
Click here to check amazing Say Me content. Otherwise, check out these important facts you probably never knew about say-me.de
Ganz nach Ihren Wünschen präsentiere ich Ihnen die neuesten Radio-Hits, die Charts und das Beste der vergangenen Jahre, 60er, 70er, 80er, 90er, mit meiner mobilen Diskothek, bei ihnen vor Ort.
Visit say-me.deWe analyzed Say-me.de page load time and found that the first response time was 251 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
say-me.de performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value10.5 s
0/100
25%
Value11.5 s
5/100
10%
Value7,650 ms
0/100
30%
Value0.03
100/100
15%
Value26.1 s
0/100
10%
251 ms
286 ms
33 ms
89 ms
49 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Say-me.de, 26% (38 requests) were made to Static.parastorage.com and 12% (18 requests) were made to Google-calendar.galilcloud.wixapps.net. The less responsive or slowest element that took the longest time to load (878 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.4 MB (31%)
10.7 MB
7.4 MB
In fact, the total size of Say-me.de main page is 10.7 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. 85% 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. Images take 6.5 MB which makes up the majority of the site volume.
Potential reduce by 373 B
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 373 B or 43% of the original size.
Potential reduce by 113.1 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. Say Me images are well optimized though.
Potential reduce by 3.0 MB
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 3.0 MB or 76% of the original size.
Potential reduce by 243.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. Say-me.de needs all CSS files to be minified and compressed as it can save up to 243.5 kB or 86% of the original size.
Number of requests can be reduced by 90 (66%)
136
46
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Say Me. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
say-me.de
251 ms
www.infinitydj.de
286 ms
infinitydj
33 ms
bt
89 ms
require.min.js
49 ms
main-r.min.js
52 ms
viewer.css
95 ms
dynamicmodel
30 ms
10f4c4_dcf4ef59f425767c848354c7b3bf66e8_712.json.z
280 ms
10f4c4_b07fd5cfa94de605b9d2eba10f69d65c_701.json.z
432 ms
ugc-viewer
77 ms
bt
82 ms
skins.min.js
267 ms
components.min.js
75 ms
utils.min.js
149 ms
core.min.js
71 ms
react-with-addons.min.js
140 ms
lodash.min.js
25 ms
TweenMax.min.js
37 ms
layout.min.js
67 ms
tpa.min.js
70 ms
fonts.min.js
136 ms
animations.min.js
136 ms
swfobject.min.js
137 ms
mousetrap.min.js
136 ms
tweenEngine.min.js
138 ms
DrawSVGPlugin.min.js
138 ms
react-dom.min.js
135 ms
ScrollToPlugin.min.js
135 ms
widgets.min.js
136 ms
experiment.js
136 ms
render.min.js
139 ms
wixappsCore.min.js
135 ms
wixappsClassics.min.js
137 ms
wixappsBuilder.min.js
134 ms
zepto.min.js
133 ms
color.min.js
132 ms
react-dom-server.min.js
18 ms
bt
57 ms
latin.css
174 ms
dc.js
135 ms
bt
432 ms
10f4c4_f42288d9fa094624b35812e3ff925a34.jpg
333 ms
wf_label_static.png
230 ms
css
225 ms
google-calendar.galilcloud.wixapps.net
253 ms
widget
241 ms
hitcounter.galilcloud.wixapps.net
234 ms
index.html
237 ms
da00086a27cc2c52ec7a11ec468c4d29.wix_mp
117 ms
10f4c4_16554a2e78c44ba3a65ad77c02ad237b.jpg
494 ms
214ec6_20c3bcf6a4fca13989b6c86fb8acd47e.png
588 ms
214ec6_27b0e0da07f785bc25cb7af81c26c9eb.png
590 ms
10f4c4_e41443bfbbe849408cee7db16115654c.jpg
579 ms
10f4c4_923242ed84ae43d0946a8c6c0a2bfe54.jpg
585 ms
10f4c4_7b1dd53f33a14bac96a9cc624c12ec85.jpg
577 ms
10f4c4_f42288d9fa094624b35812e3ff925a34.jpg
606 ms
10f4c4_c09289a6cf9c44d9be9076a78cf72450.png
878 ms
10f4c4_a51e596109654d5498e648402132f0d2.jpg
679 ms
214ec6_d062ff4a53820f13b6f31006b24e4fd6.png
585 ms
10f4c4_923242ed84ae43d0946a8c6c0a2bfe54.jpg
677 ms
bt
116 ms
bt
445 ms
bt
444 ms
BG91x1.jpg
114 ms
arrows_white_new3.png
119 ms
apple_box.png
118 ms
page.css
102 ms
animations.css
107 ms
animate.css
109 ms
jquery.min.js
354 ms
wix.min.js
375 ms
jquery.cookie.js
114 ms
lib.js
112 ms
ready.js
113 ms
model.js
113 ms
bb601a62.app.css
111 ms
Wix.js
433 ms
jquery.min.js
430 ms
angular.min.js
444 ms
5e3d5fdf.app.js
336 ms
widget.css
441 ms
flexcrollstyles.css
442 ms
telething.css
443 ms
jquery.min.js
429 ms
wix.min.js
366 ms
flexcroll.js
442 ms
widget.js
465 ms
telething.js
468 ms
mySlideshow.js
472 ms
common.js
473 ms
bootstrap.3.1.1.min.css
331 ms
popover-extra-placements.css
339 ms
fontFace.css
323 ms
css
324 ms
widget.css
337 ms
wix.min.js
322 ms
jquery.1.10.2.min.js
356 ms
bootstrap.min.js
357 ms
angular.min.js
417 ms
jquery.slimscroll.min.js
419 ms
moment.min.js
419 ms
fullcalendar.js
458 ms
fullcalendar-all-langs.js
460 ms
gcal.js
417 ms
functions2.js
460 ms
functions.js
459 ms
widget.js
457 ms
BaRU3GSISDJW2nIqbysbmg.ttf
244 ms
TSDaXhyJuDJ-NBU0popSWA.ttf
258 ms
5t8vP9Hx2udzw372glmOxA.ttf
246 ms
opensans-regular-webfont.woff
350 ms
opensans-bold-webfont.woff
351 ms
fullcalendar.min.css
213 ms
150 ms
nr-885.min.js
145 ms
analytics.js
109 ms
uploadToTelething.html
376 ms
getDropboxImgsLinks
810 ms
transparent600X400.png
160 ms
ezgif_loader.gif
162 ms
slideshow_prev.png
160 ms
slideshow_next.png
160 ms
slideshow_pause.png
162 ms
slideshow_upload.png
162 ms
xBW.jpg
170 ms
ugc-viewer
87 ms
preloader.GIF
78 ms
metal_bg.png
78 ms
css
62 ms
load
193 ms
app.html
190 ms
metal_bg.png
165 ms
7800adffd0
172 ms
214ec6_d062ff4a53820f13b6f31006b24e4fd6.png
108 ms
icon3.html
77 ms
vi.jpg
141 ms
x.jpg
213 ms
File%20Types%20Jpg.ico
613 ms
collect
78 ms
i.js
84 ms
d591a0253e4e11e69e13749d4191a3f43efe0bec.1.js
85 ms
events
157 ms
leftarrow.svg
47 ms
rightarrow.svg
43 ms
Logo%20InfinityDJ.jpg
271 ms
7800adffd0
23 ms
File%20Types%20Jpg.ico
425 ms
say-me.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
say-me.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
say-me.de SEO score
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 Say-me.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 Say-me.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.
say-me.de
Open Graph description is not detected on the main page of Say Me. 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: