2.3 sec in total
392 ms
1.8 sec
136 ms
Click here to check amazing Berryware content. Otherwise, check out these important facts you probably never knew about berryware.com
Visit berryware.comWe analyzed Berryware.com page load time and found that the first response time was 392 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
berryware.com performance score
name
value
score
weighting
Value1.5 s
95/100
10%
Value1.5 s
100/100
25%
Value1.6 s
100/100
10%
Value20 ms
100/100
30%
Value0.053
98/100
15%
Value1.5 s
100/100
10%
392 ms
93 ms
258 ms
255 ms
258 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that all of those requests were addressed to Berryware.com and no external sources were called. The less responsive or slowest element that took the longest time to load (520 ms) belongs to the original domain Berryware.com.
Page size can be reduced by 52.3 kB (30%)
171.8 kB
119.5 kB
In fact, the total size of Berryware.com main page is 171.8 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. 15% of websites need less resources to load. Images take 113.5 kB which makes up the majority of the site volume.
Potential reduce by 12.6 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 12.6 kB or 83% of the original size.
Potential reduce by 4.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. Berryware images are well optimized though.
Potential reduce by 32.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 32.4 kB or 81% of the original size.
Potential reduce by 2.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. Berryware.com needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 79% of the original size.
Number of requests can be reduced by 67 (68%)
98
31
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berryware. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
berryware.com
392 ms
main.css
93 ms
x_core.js
258 ms
x_event.js
255 ms
x_win.js
258 ms
x_slide.js
257 ms
kb_ext.js
204 ms
bwws_main.js
204 ms
header_spacer.png
108 ms
berryware_header.png
216 ms
menubar_spacer.png
102 ms
menubar_block1.png
93 ms
menubar_sep1.png
110 ms
menubar_button1.png
100 ms
menubar_sep2.png
166 ms
menubar_button2.png
168 ms
menubar_sep3.png
167 ms
menubar_button3.png
179 ms
menubar_sep4.png
179 ms
menubar_button4.png
235 ms
menubar_sep5.png
235 ms
menubar_button5.png
233 ms
menubar_sep6.png
250 ms
menubar_button6.png
251 ms
menubar_sep7.png
283 ms
menubar_button7.png
307 ms
menubar_sep8.png
328 ms
menubar_block3.png
306 ms
menubar_sepline.png
350 ms
contentbar_left.png
324 ms
welcome.png
413 ms
popup_line_top_IE.gif
386 ms
menubar_button1_down.png
387 ms
menubar_button1_over.png
394 ms
menubar_button2_down.png
394 ms
menubar_button2_over.png
420 ms
menubar_button3_down.png
456 ms
menubar_button3_over.png
456 ms
menubar_button4_down.png
461 ms
menubar_button4_over.png
463 ms
menubar_button5_down.png
474 ms
menubar_button5_over.png
483 ms
menubar_button6_down.png
520 ms
menubar_button6_over.png
505 ms
menubar_button7_down.png
446 ms
menubar_button7_over.png
437 ms
menubar_sep1_rdown.png
449 ms
menubar_sep1_rover.png
452 ms
menubar_sep2_ldown.png
486 ms
menubar_sep2_ldown_rdown.png
428 ms
menubar_sep2_ldown_rover.png
437 ms
menubar_sep2_lover.png
438 ms
menubar_sep2_lover_rdown.png
436 ms
menubar_sep2_rdown.png
446 ms
menubar_sep2_rover.png
447 ms
menubar_sep3_ldown.png
426 ms
menubar_sep3_ldown_rover.png
434 ms
menubar_sep3_lover.png
434 ms
menubar_sep3_lover_rdown.png
428 ms
menubar_sep3_rdown.png
437 ms
menubar_sep3_rover.png
441 ms
menubar_sep4_ldown.png
416 ms
menubar_sep4_ldown_rover.png
425 ms
menubar_sep4_lover.png
408 ms
menubar_sep4_lover_rdown.png
415 ms
menubar_sep4_rdown.png
403 ms
menubar_sep4_rover.png
399 ms
menubar_sep5_ldown.png
399 ms
menubar_sep5_ldown_rover.png
401 ms
menubar_sep5_lover.png
401 ms
menubar_sep5_lover_rdown.png
393 ms
menubar_sep5_rdown.png
397 ms
menubar_sep5_rover.png
394 ms
menubar_sep6_ldown.png
395 ms
menubar_sep6_ldown_rover.png
405 ms
menubar_sep6_lover.png
401 ms
menubar_sep6_lover_rdown.png
395 ms
menubar_sep6_rdown.png
398 ms
menubar_sep6_rover.png
395 ms
menubar_sep7_ldown.png
397 ms
menubar_sep7_ldown_rover.png
401 ms
menubar_sep7_lover.png
404 ms
menubar_sep7_lover_rdown.png
395 ms
menubar_sep7_rdown.png
402 ms
menubar_sep7_rover.png
396 ms
menubar_sep8_ldown.png
396 ms
menubar_sep8_lover.png
400 ms
popup_line_top.png
401 ms
popup_line_bottom.png
395 ms
popup_item_products_spacer.png
399 ms
popup_item_products_n1.png
396 ms
popup_item_products_h1.png
396 ms
popup_item_products_n2.png
401 ms
popup_item_products_h2.png
401 ms
popup_item_products_n3.png
394 ms
popup_item_products_h3.png
400 ms
popup_item_products_n4.png
394 ms
popup_item_products_h4.png
397 ms
javascriptrequired.gif
402 ms
berryware.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
berryware.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
berryware.com SEO score
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
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berryware.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Berryware.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
berryware.com
Open Graph description is not detected on the main page of Berryware. 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: