6.3 sec in total
1.4 sec
4.6 sec
286 ms
Visit palatineroses.com now to see the best up-to-date Palatine Roses content for United States and also check out these interesting facts you probably never knew about palatineroses.com
Palatine Fruit & Roses is a sustainable family-owned tender fruit farm, rose nursery, cut rose grower, and garden centre in Niagara, Ontario.
Visit palatineroses.comWe analyzed Palatineroses.com page load time and found that the first response time was 1.4 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
palatineroses.com performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value16.7 s
0/100
25%
Value10.2 s
8/100
10%
Value1,910 ms
8/100
30%
Value0.01
100/100
15%
Value20.3 s
2/100
10%
1408 ms
2307 ms
2318 ms
2761 ms
270 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 94% of them (51 requests) were addressed to the original Palatineroses.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Gavamedia.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Palatineroses.com.
Page size can be reduced by 132.7 kB (11%)
1.2 MB
1.1 MB
In fact, the total size of Palatineroses.com main page is 1.2 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 7.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. 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 7.0 kB or 67% of the original size.
Potential reduce by 125.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. Obviously, Palatine Roses needs image optimization as it can save up to 125.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 50 B
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.
We found no issues to fix!
50
50
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Palatine Roses. According to our analytics all requests are already optimized.
palatineroses.com
1408 ms
s.css
2307 ms
b.css
2318 ms
s.js
2761 ms
bg_big.jpg
270 ms
header_bg_big.jpg
161 ms
header.png
302 ms
cart.png
163 ms
header_bottom.jpg
218 ms
slideshow.png
271 ms
slide0-pic.jpg
271 ms
slide1-pic.jpg
274 ms
slide2-pic.jpg
325 ms
slide3-pic.jpg
329 ms
slide4-pic.jpg
330 ms
slideshow_left.png
332 ms
slideshow_right.png
350 ms
slideshow_nav_left.png
380 ms
slideshow_nav_hover.jpg
386 ms
slideshow_nav_btn.jpg
385 ms
slideshow_nav_right.png
386 ms
arrow.png
401 ms
search.png
435 ms
russet_rose.jpg
441 ms
pink_rose.jpg
446 ms
mauve_rose.jpg
445 ms
striped_rose.jpg
462 ms
orange_rose.jpg
475 ms
red_rose.jpg
490 ms
white_rose.jpg
495 ms
yellow_rose.jpg
501 ms
closed.png
555 ms
garden_roses.jpg
500 ms
fresh_cut_roses.jpg
532 ms
garden_ideas.jpg
544 ms
fresh_local_fruit.jpg
548 ms
footer.jpg
553 ms
catalogue_right_footer.png
554 ms
catalogue_right.png
653 ms
browsers.gif
225 ms
helvetica-condensed-black.woff
454 ms
YanoneKaffeesatz-Regular.woff
458 ms
f.woff
407 ms
footer-palatine-roses.jpg
356 ms
love-of-roses-big.png
354 ms
connect.jpg
409 ms
pinterest.jpg
407 ms
youtube.jpg
382 ms
facebook.jpg
354 ms
twitter.jpg
348 ms
analytics.js
25 ms
slideshow_left_hover.png
308 ms
slideshow_right_hover.png
310 ms
collect
12 ms
palatineroses.com accessibility score
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
[id] attributes on active, focusable elements are not unique
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
palatineroses.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Palatineroses.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 Palatineroses.com 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.
palatineroses.com
Open Graph description is not detected on the main page of Palatine Roses. 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: