3 sec in total
271 ms
1.9 sec
796 ms
Welcome to silverberry.net homepage info - get ready to check Silverberry best content right away, or after learning these important things about silverberry.net
Come and relax over breakfast, brunch, lunch or beautifully made artisan coffee and homemade cakes in Silverberry’s warm and welcoming local atmosphere.
Visit silverberry.netWe analyzed Silverberry.net page load time and found that the first response time was 271 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
silverberry.net performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value7.1 s
6/100
25%
Value7.6 s
26/100
10%
Value550 ms
53/100
30%
Value0
100/100
15%
Value10.9 s
21/100
10%
271 ms
446 ms
93 ms
176 ms
337 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 69% of them (59 requests) were addressed to the original Silverberry.net, 21% (18 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (808 ms) belongs to the original domain Silverberry.net.
Page size can be reduced by 111.2 kB (11%)
993.0 kB
881.9 kB
In fact, the total size of Silverberry.net main page is 993.0 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. Javascripts take 470.1 kB which makes up the majority of the site volume.
Potential reduce by 97.8 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 97.8 kB or 82% of the original size.
Potential reduce by 9.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. Silverberry images are well optimized though.
Potential reduce by 2.6 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.
Potential reduce by 1.2 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. Silverberry.net has all CSS files already compressed.
Number of requests can be reduced by 58 (89%)
65
7
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Silverberry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
silverberry.net
271 ms
silverberry.net
446 ms
animate.min.css
93 ms
elegant-icons.min.css
176 ms
all.min.css
337 ms
styles.css
251 ms
grid.css
255 ms
main.css
252 ms
sr7.css
257 ms
grid.min.css
258 ms
helper-parts.min.css
334 ms
main.min.css
420 ms
perfect-scrollbar.css
345 ms
swiper.min.css
343 ms
main.min.css
441 ms
fidalgo-core.min.css
506 ms
css
35 ms
style.css
415 ms
css
44 ms
elementor.min.css
438 ms
frontend.min.css
434 ms
e-swiper.min.css
498 ms
post-8.css
503 ms
global.css
520 ms
post-11674.css
521 ms
css
44 ms
jquery.min.js
535 ms
jquery-migrate.min.js
581 ms
tptools.js
712 ms
sr7.js
711 ms
fadeIn.min.css
691 ms
widget-image.min.css
693 ms
widget-rating.min.css
692 ms
widget-heading.min.css
708 ms
widget-spacer.min.css
709 ms
widget-google_maps.min.css
707 ms
hooks.min.js
708 ms
i18n.min.js
808 ms
index.js
808 ms
index.js
808 ms
main.js
807 ms
core.min.js
724 ms
main.min.js
700 ms
perfect-scrollbar.jquery.min.js
642 ms
hoverIntent.min.js
665 ms
modernizr.js
639 ms
gsap.min.js
731 ms
ScrollTrigger.min.js
670 ms
jquery.parallax-scroll.js
614 ms
main.min.js
629 ms
fidalgo-core.min.js
642 ms
swiper.min.js
740 ms
accordion.min.js
592 ms
webpack.runtime.min.js
605 ms
frontend-modules.min.js
614 ms
frontend.min.js
597 ms
elementor.js
596 ms
elementor.min.js
600 ms
sb-logo-green.png
587 ms
silverberry-interior-home-2-s-qrq33inwrydz12m8vte28c49kvvu7qn7qi0wb8ln5c.jpg
522 ms
silverberry-interior-home-1-qrfwlwp7w9bwe32mat0dvp4u6lic0gxds6z2rawcc0.jpg
609 ms
silverberry-interior-home-3-s-qrq34jbm6hs5lv4zxr8ifkv8qwv5jxoqvjgu113aeo.jpg
527 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JTVBNI4.woff
52 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JTVPNI4.woff
91 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJTVBNI4.woff
109 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJTVPNI4.woff
152 ms
92zPtBhPNqw79Ij1E865zBUv7myjJDVBNI4.woff
111 ms
92zPtBhPNqw79Ij1E865zBUv7myjJDVPNI4.woff
112 ms
92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI4.woff
111 ms
92zPtBhPNqw79Ij1E865zBUv7myjJTVPNI4.woff
112 ms
92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI4.woff
110 ms
92zPtBhPNqw79Ij1E865zBUv7myRJTVPNI4.woff
152 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IjVBNI4.woff
153 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IjVPNI4.woff
153 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIjVBNI4.woff
152 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIjVPNI4.woff
151 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIjVBNI4.woff
151 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIjVPNI4.woff
152 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIjVBNI4.woff
152 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIjVPNI4.woff
152 ms
embed
378 ms
js
38 ms
search.js
3 ms
geometry.js
7 ms
main.js
14 ms
silverberry.net accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
silverberry.net 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
silverberry.net SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Silverberry.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Silverberry.net 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.
silverberry.net
Open Graph description is not detected on the main page of Silverberry. 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: