6 sec in total
602 ms
4.8 sec
627 ms
Welcome to dasberlinblog.de homepage info - get ready to check Das Berlin Blog best content right away, or after learning these important things about dasberlinblog.de
Die Top Sehenswürdigkeiten in Berlin, Ausflugsziele, Geheimtipps und Ausflüge mit Kindern finden Sie hier. Außerdem Tickets und Unterkünfte in Berlin.
Visit dasberlinblog.deWe analyzed Dasberlinblog.de page load time and found that the first response time was 602 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dasberlinblog.de performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value2.6 s
87/100
25%
Value4.1 s
78/100
10%
Value10 ms
100/100
30%
Value0.075
95/100
15%
Value3.6 s
92/100
10%
602 ms
91 ms
179 ms
313 ms
182 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 37% of them (47 requests) were addressed to the original Dasberlinblog.de, 15% (19 requests) were made to Ih.adscale.de and 12% (15 requests) were made to Dmp.theadex.com. The less responsive or slowest element that took the longest time to load (833 ms) belongs to the original domain Dasberlinblog.de.
Page size can be reduced by 824.4 kB (39%)
2.1 MB
1.3 MB
In fact, the total size of Dasberlinblog.de main page is 2.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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 61.0 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 10.7 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 61.0 kB or 82% of the original size.
Potential reduce by 74.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. Das Berlin Blog images are well optimized though.
Potential reduce by 646.4 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 646.4 kB or 71% of the original size.
Potential reduce by 42.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. Dasberlinblog.de needs all CSS files to be minified and compressed as it can save up to 42.5 kB or 83% of the original size.
Number of requests can be reduced by 79 (71%)
112
33
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Das Berlin Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.dasberlinblog.de
602 ms
style.css
91 ms
pagenavi-css.css
179 ms
jquery.js
313 ms
jquery-migrate.min.js
182 ms
lightbox.css
184 ms
prototype.js
190 ms
scriptaculous.js
191 ms
lightbox.js
265 ms
praeludium_testroom.js
392 ms
prototype.js
391 ms
adition.js
363 ms
secure_tag_head_adfarm1.js
389 ms
secure_tag_before_body_end.js
281 ms
front.asp
206 ms
wp-emoji-release.min.js
167 ms
ga.js
29 ms
effects.js
91 ms
__utm.gif
11 ms
adex.js
253 ms
rc
216 ms
koeln-allgemein_mono.gif
89 ms
koeln-allgemein_rgb.gif
92 ms
millionenstaedte_mono.gif
92 ms
millionenstaedte_rgb.gif
94 ms
frankfurter-rundblick_mono.gif
89 ms
frankfurter-rundblick_rgb.gif
94 ms
hamburger_allee_mono.gif
176 ms
hamburger_allee_rgb.gif
176 ms
muenchener-rundschau_mono.gif
180 ms
muenchener-rundschau_rgb.gif
181 ms
homeoffice.jpg
465 ms
berlin.jpg
653 ms
Tipps-So-planen-Sie-ein-oeffentliches-Event-300x199.jpg
350 ms
Mitarbeiterzufriedenheit.jpg
614 ms
Werbellinsee.jpg
540 ms
Berlin-Kultur.jpg
580 ms
Britzer-Garten-Berlin.jpg
833 ms
Berlin-Stadt.jpg
651 ms
gartenzwerg-300x199.jpg
631 ms
Haus-Schluessel-300x200.jpg
670 ms
search.gif
701 ms
just2guide.png
724 ms
call.sjs
107 ms
Rest;sz=728x90,728x180;adset=bsl;;tile=1;prae=y;flash=no;adset=f;ord=26074529583
249 ms
Cookie
106 ms
t.js
87 ms
1.gif
89 ms
analytic.js
177 ms
173 ms
getads.js
6 ms
t.js
120 ms
pixel
19 ms
redirect
193 ms
cm.gif
88 ms
impr
122 ms
2.gif
86 ms
redirect
344 ms
adex.js
172 ms
rtb
103 ms
match
94 ms
js
280 ms
1.gif
88 ms
analytic.js
89 ms
88 ms
loadImages.js
18 ms
0
96 ms
2.gif
89 ms
2.gif
89 ms
nuggad
91 ms
banner
174 ms
callback.js
3 ms
impr
102 ms
adex.js
168 ms
mtrcs_284704.js
298 ms
Rest;sz=120x600,160x600,200x600,300x600;adset=bsl;;tile=2;prae=y;flash=no;adset=f;ord=26074529583
273 ms
127
95 ms
2.gif
88 ms
impr
119 ms
mtrcs_284704.js
80 ms
593
96 ms
rtb
99 ms
js
174 ms
887
96 ms
banner
177 ms
impr
124 ms
mtrcs_284704.js
95 ms
bg_header.jpg
480 ms
wrapper.jpg
277 ms
side_left.gif
92 ms
side_right.gif
95 ms
side_top.gif
89 ms
side_bot.gif
96 ms
left_top.gif
178 ms
right_top.jpg
184 ms
left_bot.gif
187 ms
right_bot.gif
193 ms
arr_1.gif
266 ms
main_menu_hover.gif
520 ms
Rest;sz=2x2;adset=bsl;dcopt=ist;;tile=3;prae=y;flash=no;adset=f;ord=26074529583
66 ms
1166
94 ms
pixel
37 ms
getads.js
19 ms
impr
98 ms
gum
261 ms
rtb
97 ms
bg_footer.gif
277 ms
load
82 ms
js
275 ms
pixel
13 ms
itxtcss_1446206988.css
74 ms
underscore-min-ns-1.4.2.js
78 ms
core_1446569672.js
81 ms
data_1444835675.js
107 ms
debug_1395261999.js
82 ms
fx_1395261999.js
83 ms
fx2_1395261999.js
110 ms
itxt_1426253035.js
111 ms
metrics_1395261999.js
110 ms
tmpl_1443709758.js
118 ms
ui_1447845393.js
159 ms
ui_mobile_1423653241.js
143 ms
1921
94 ms
0
120 ms
px.gif
39 ms
init
94 ms
loading.gif
36 ms
usersync.aspx
18 ms
dasberlinblog.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
dasberlinblog.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
dasberlinblog.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Dasberlinblog.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 Dasberlinblog.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.
dasberlinblog.de
Open Graph description is not detected on the main page of Das Berlin Blog. 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: