5.5 sec in total
1.1 sec
4.1 sec
314 ms
Click here to check amazing Berryblog content. Otherwise, check out these important facts you probably never knew about berryblog.de
Visit berryblog.deWe analyzed Berryblog.de page load time and found that the first response time was 1.1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
berryblog.de performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value1.7 s
99/100
25%
Value1.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.7 s
100/100
10%
1140 ms
313 ms
227 ms
213 ms
424 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 27% of them (39 requests) were addressed to the original Berryblog.de, 7% (10 requests) were made to Gravatar.com and 7% (10 requests) were made to Rtb-csync.smartadserver.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Berryblog.de.
Page size can be reduced by 174.2 kB (32%)
547.4 kB
373.2 kB
In fact, the total size of Berryblog.de main page is 547.4 kB. 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 294.8 kB which makes up the majority of the site volume.
Potential reduce by 36.4 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 36.4 kB or 76% of the original size.
Potential reduce by 12.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. Berryblog images are well optimized though.
Potential reduce by 81.5 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 81.5 kB or 53% of the original size.
Potential reduce by 43.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. Berryblog.de needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 86% of the original size.
Number of requests can be reduced by 74 (58%)
128
54
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berryblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.berryblog.de
1140 ms
style.css
313 ms
dropmenu.css
227 ms
comments.css
213 ms
dropmenu.jquery.js
424 ms
dropmenu.js
224 ms
juiz-social-post-sharer-1.min.css
326 ms
view.asp
365 ms
show_ads.js
6 ms
asw.js
254 ms
ad.php
671 ms
wp-emoji-release.min.js
148 ms
avatar.php
89 ms
navbg.png
142 ms
navbg-b.png
144 ms
headerbg.png
142 ms
logo_w.jpg
143 ms
BlackBerry_Pee_3-150x150.jpg
145 ms
BlackBerry10-hands-on-engadget-150x150.jpg
228 ms
blackberry-wolrd-2012-keynote-3-150x150.jpg
239 ms
BlackBerry-World-2012-1-150x150.jpg
255 ms
blackberry-blade-vorschau.jpg
245 ms
BlackBerry-Bridge-2.0-150x150.jpg
248 ms
wpid-IMG_20131124_edit-150x150.png
246 ms
ISEC7_logo_RGB-150x150.jpg
344 ms
blackberry-whatsapp-150x150.jpg
365 ms
Bebuzz_logo_150x150.jpg
346 ms
playbook_high_capicity_charger_klein.jpg
363 ms
BlackBerry_Live_logo.jpg
363 ms
BlackBerry_Travel_Logo.jpg
371 ms
blackberry-link-hero-150x150.jpg
496 ms
firmware.jpg
497 ms
demos1.jpg
497 ms
bb-9900-os.jpg
586 ms
bold-9790-os.jpg
505 ms
playbook1-150x150.jpg
512 ms
bell-rim-lpaybook-lte-4g-150x150.png
693 ms
blackberry-playbook-wide-150x150.jpg
602 ms
avatar.php
164 ms
avatar.php
166 ms
avatar.php
167 ms
avatar.php
203 ms
navbg2.png
681 ms
navbg2-b.png
682 ms
shadowoverlay-trans-150.png
686 ms
overlay.png
683 ms
ca-pub-3665106632391333.js
39 ms
zrt_lookup.html
28 ms
show_ads_impl.js
52 ms
sidebar.png
655 ms
ads-common.js
244 ms
1b4fcae4b163a2021b17174986c317b2
61 ms
ads
268 ms
osd.js
8 ms
ads
242 ms
c3c3d2756da26856202262447cbb1e28
29 ms
a51915181528cf391c860c367daf8bb7
27 ms
dab8ad826c70c9967ea7567e67a79193
27 ms
d41d8cd98f00b204e9800998ecf8427e
29 ms
cm
210 ms
12726627775957807320
44 ms
abg.js
47 ms
m_js_controller.js
56 ms
googlelogo_color_112x36dp.png
42 ms
cm.php
171 ms
s
39 ms
x_button_blue2.png
39 ms
nessie_icon_tiamat_white.png
11 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
9 ms
31jVaqgb5tL._SX60_SY80_.jpg
94 ms
187 ms
51IHIx52izL._SX60_SY80_.jpg
89 ms
41dnV12dHRL._SX60_SY80_.jpg
89 ms
41T2QyZ5AZL._SX60_SY80_.jpg
90 ms
footerbg.png
136 ms
view_n.php
111 ms
ga.js
68 ms
51IHIx52izL._OU03_SL60_PI20-percent,BottomRight,0,0_CR0,0,60,47_.jpg
59 ms
000000549450.gif
622 ms
__utm.gif
13 ms
ac
337 ms
show1.asp
86 ms
CookieSync.html
8 ms
jsinfo.asp
109 ms
quant.js
19 ms
CookieSync.min.js
4 ms
pixel.htm
38 ms
usermatch
18 ms
pixelpush
11 ms
p68r
75 ms
generic
12 ms
pixel
23 ms
sync
16 ms
generic
12 ms
usermatch
18 ms
78 ms
109 ms
111 ms
gr
49 ms
casale
10 ms
pixel
17 ms
VupTiMAoJV4AAMgDcbQAAAAI%26635
102 ms
59 ms
csle
39 ms
GenericUserSync.ashx
15 ms
100 ms
ddc.htm
30 ms
100 ms
pixel;r=1288389528;a=p-T1nhLcmCjVzQS;fpan=1;fpa=P0-183137736-1458197384968;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458197384968;tzo=-180;ref=http%3A%2F%2Fwww.usemax.de%2Fview_n.php%3Fwf%3D3%26userid%3D4848%26w%3D4848%26visible%3D1%26channel%3D25%26subid%3D%26referrer%3Dhttp%253A%252F%252Fwww.berryblog.de%252F%26imp%3D897873%26nt%3D2%26timeout%3D0%26rd%3D;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1364%26dcid%3D6;ogl=
9 ms
crum
47 ms
95 ms
rum
103 ms
113 ms
rum
51 ms
crum
91 ms
Pug
95 ms
pixel
42 ms
rtset
95 ms
u.php
78 ms
um
197 ms
rum
68 ms
90 ms
pixel
102 ms
bd
87 ms
crum
56 ms
merge
49 ms
tap.php
57 ms
rum
53 ms
match
52 ms
sd
26 ms
sync
41 ms
view_n.php
112 ms
mapuser
31 ms
xrefid.xgi
29 ms
lr.gif
16 ms
bd
23 ms
NAX3633657757570584468
42 ms
34 ms
m
29 ms
pixel.gif
13 ms
crum
11 ms
cm
87 ms
30 ms
activeview
13 ms
activeview
19 ms
VXD-257-House-728x90-DE.jpg
17 ms
83 ms
berryblog.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
<frame> or <iframe> elements do not have a title
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.
berryblog.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
berryblog.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
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berryblog.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), while the claimed language is German. Our system also found out that Berryblog.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.
berryblog.de
Open Graph description is not detected on the main page of Berryblog. 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: