Tools & Wizards About Us
berryme.de screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

berryme.de

BerryMe.de - das BlackBerry Blog mit Testberichten, Neuigkeiten uvm.

Page Load Speed

6.6 sec in total

First Response

110 ms

Resources Loaded

5.8 sec

Page Rendered

692 ms

berryme.de screenshot

About Website

Visit berryme.de now to see the best up-to-date Berry Me content for Germany and also check out these interesting facts you probably never knew about berryme.de

BerryMe.de ist ein Blog über BlackBerry Smartphones und Tablets. Neben Testberichten zu aktuellen Geräten gibt es Neuigkeiten und Tipps rund um das Thema

Visit berryme.de

Key Findings

We analyzed Berryme.de page load time and found that the first response time was 110 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

berryme.de performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

berryme.de

110 ms

berryme.de

411 ms

style.css

381 ms

colorbox.css

428 ms

style.min9dff.css

519 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 73% of them (68 requests) were addressed to the original Berryme.de, 20% (19 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Secure.gravatar.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Berryme.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.0 kB (8%)

Content Size

711.6 kB

After Optimization

651.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Berryme.de main page is 711.6 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. 70% of websites need less resources to load. Images take 613.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 48.5 kB

  • Original 61.9 kB
  • After minification 54.5 kB
  • After compression 13.5 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 7.4 kB, which is 12% 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 48.5 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 11.5 kB

  • Original 613.7 kB
  • After minification 602.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. Berry Me images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 36.0 kB
  • After minification 36.0 kB
  • After compression 36.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 41 (47%)

Requests Now

88

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berry 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 17 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

berryme.de

berryme.de

110 ms

berryme.de

berryme.de

411 ms

style.css

style.css

381 ms

colorbox.css

colorbox.css

428 ms

style.min9dff.css

style.min9dff.css

519 ms

stylesb62d.css

stylesb62d.css

519 ms

cookie-law-info-public4511.css

cookie-law-info-public4511.css

420 ms

cookie-law-info-gdpr4511.css

cookie-law-info-gdpr4511.css

521 ms

screen.min673a.css

screen.min673a.css

749 ms

wpfront-notification-bar4735.css

wpfront-notification-bar4735.css

758 ms

60fc4a56bde4fd10260a786c13ce28e0

60fc4a56bde4fd10260a786c13ce28e0

33 ms

likebox.php

likebox.php

335 ms

rocket-loader.min.js

rocket-loader.min.js

759 ms

berryme.png

berryme.png

748 ms

ThumbFacebookCalender-600x495.png

ThumbFacebookCalender-600x495.png

758 ms

Facebook-Events-600x539.png

Facebook-Events-600x539.png

953 ms

2016-01-26-12.24.29-150x150.png

2016-01-26-12.24.29-150x150.png

1106 ms

2016-01-26-12.24.52-150x150.png

2016-01-26-12.24.52-150x150.png

1129 ms

2016-01-26-12.25.05-150x150.png

2016-01-26-12.25.05-150x150.png

1135 ms

2016-01-26-12.25.24-150x150.png

2016-01-26-12.25.24-150x150.png

1139 ms

2016-01-26-12.26.04-150x150.png

2016-01-26-12.26.04-150x150.png

1133 ms

2016-01-26-12.26.18-150x150.png

2016-01-26-12.26.18-150x150.png

1324 ms

2016-01-26-12.26.38-150x150.png

2016-01-26-12.26.38-150x150.png

1482 ms

BlackBerry-Logo-600x384.jpg

BlackBerry-Logo-600x384.jpg

1509 ms

2015-12-08-14.22.40-600x1067.png

2015-12-08-14.22.40-600x1067.png

1513 ms

IMG_20151208_162634-1-600x600.jpg

IMG_20151208_162634-1-600x600.jpg

1523 ms

BerryMe_PB081698-600x450.jpg

BerryMe_PB081698-600x450.jpg

1519 ms

facebook.png

facebook.png

1699 ms

twitter.png

twitter.png

1846 ms

rss.png

rss.png

1890 ms

BlackBerry_PRIV_1-50x50.jpg

BlackBerry_PRIV_1-50x50.jpg

1882 ms

4.png

4.png

1904 ms

DSC03630bq-e1423045582713-50x50.jpg

DSC03630bq-e1423045582713-50x50.jpg

1894 ms

4.5.png

4.5.png

2071 ms

BlackBerry-Passport-Review-50x50.jpg

BlackBerry-Passport-Review-50x50.jpg

2217 ms

5.png

5.png

2257 ms

Weihnachtsgewinnspiel-50x50.jpg

Weihnachtsgewinnspiel-50x50.jpg

2261 ms

Bold-9790-50x50.jpg

Bold-9790-50x50.jpg

2263 ms

BlackBerry-Q10-Bildschirm-50x50.jpg

BlackBerry-Q10-Bildschirm-50x50.jpg

2290 ms

dbe63ded5bf99dc58c1af870d060ab8a

dbe63ded5bf99dc58c1af870d060ab8a

29 ms

9f30bbe5669d4ce56545230c78daa242

9f30bbe5669d4ce56545230c78daa242

30 ms

ThumbFacebookCalender-50x50.png

ThumbFacebookCalender-50x50.png

2436 ms

J8EZh-mB0NT.css

J8EZh-mB0NT.css

33 ms

PgnZuKA5du5.css

PgnZuKA5du5.css

37 ms

f3r3JT4KQH9.css

f3r3JT4KQH9.css

36 ms

Pvak98mlgyI.js

Pvak98mlgyI.js

47 ms

guwKwycnxkZ.js

guwKwycnxkZ.js

41 ms

E_P-TzY6wm3.js

E_P-TzY6wm3.js

41 ms

hioPldJUw08.js

hioPldJUw08.js

40 ms

fFBZSPO6Swz.js

fFBZSPO6Swz.js

46 ms

p55HfXW__mM.js

p55HfXW__mM.js

78 ms

ALTQi95mOyD.js

ALTQi95mOyD.js

45 ms

l7q_DlDJ6yb.js

l7q_DlDJ6yb.js

84 ms

iw-hzucRM2_.js

iw-hzucRM2_.js

89 ms

dm_fp6i6e3D.js

dm_fp6i6e3D.js

84 ms

daRG11v-d-4.js

daRG11v-d-4.js

82 ms

JZ930Hfx3Dz.js

JZ930Hfx3Dz.js

81 ms

jbkX5llFMP5.js

jbkX5llFMP5.js

83 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

113 ms

reset.css

reset.css

2226 ms

nivo-slider.css

nivo-slider.css

2228 ms

BlackBerry-Logo-50x50.jpg

BlackBerry-Logo-50x50.jpg

2190 ms

304743924_450272067153701_4569567351448927153_n.jpg

304743924_450272067153701_4569567351448927153_n.jpg

136 ms

tuZrhU49Qe0.js

tuZrhU49Qe0.js

14 ms

306449505_450272070487034_3121118621792506642_n.jpg

306449505_450272070487034_3121118621792506642_n.jpg

111 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

9 ms

2015-12-08-14.22.40-50x50.png

2015-12-08-14.22.40-50x50.png

2237 ms

IMG_20151208_162634-1-50x50.jpg

IMG_20151208_162634-1-50x50.jpg

2236 ms

BerryMe_PB081698-50x50.jpg

BerryMe_PB081698-50x50.jpg

2297 ms

top-navigation-trans.png

top-navigation-trans.png

389 ms

navigation-trans.png

navigation-trans.png

369 ms

comment-bg.png

comment-bg.png

364 ms

post-meta-bg.png

post-meta-bg.png

372 ms

author-icon.png

author-icon.png

389 ms

date-icon.png

date-icon.png

524 ms

category-icon.png

category-icon.png

737 ms

tag.png

tag.png

738 ms

ul-dot.png

ul-dot.png

738 ms

light-button.png

light-button.png

495 ms

toggle-arrow.png

toggle-arrow.png

769 ms

widget-bg.png

widget-bg.png

881 ms

social-arrow.png

social-arrow.png

883 ms

video-icon-small.png

video-icon-small.png

1114 ms

comment.png

comment.png

1114 ms

pattern7.png

pattern7.png

837 ms

totop.png

totop.png

1146 ms

PTS55F-webfont.html

PTS55F-webfont.html

1114 ms

PTN57F-webfont.html

PTN57F-webfont.html

886 ms

PTN77F-webfont.html

PTN77F-webfont.html

1166 ms

PTN57F-webfont.ttf

PTN57F-webfont.ttf

904 ms

PTS55F-webfont.ttf

PTS55F-webfont.ttf

963 ms

PTN77F-webfont.ttf

PTN77F-webfont.ttf

989 ms

jquery-1.6.4.min9dff.js

jquery-1.6.4.min9dff.js

371 ms

Accessibility Review

berryme.de accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

berryme.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

berryme.de SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berryme.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 Berryme.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.

Social Sharing Optimization

berryme.de

Open Graph description is not detected on the main page of Berry 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: