5.3 sec in total
356 ms
4.6 sec
332 ms
Click here to check amazing Roses content for Spain. Otherwise, check out these important facts you probably never knew about roses.cat
Visit roses.catWe analyzed Roses.cat page load time and found that the first response time was 356 ms 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.
roses.cat performance score
name
value
score
weighting
Value10.9 s
0/100
10%
Value20.7 s
0/100
25%
Value17.0 s
0/100
10%
Value5,910 ms
0/100
30%
Value0.185
66/100
15%
Value29.8 s
0/100
10%
356 ms
854 ms
217 ms
219 ms
234 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 93% of them (134 requests) were addressed to the original Roses.cat, 3% (4 requests) were made to Translate.googleapis.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Roses.cat.
Page size can be reduced by 277.9 kB (16%)
1.7 MB
1.5 MB
In fact, the total size of Roses.cat main page is 1.7 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 73.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. This page needs HTML code to be minified as it can gain 26.8 kB, which is 31% 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 73.0 kB or 86% of the original size.
Potential reduce by 111.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. Roses images are well optimized though.
Potential reduce by 93.2 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 93.2 kB or 39% of the original size.
Potential reduce by 70 B
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. Roses.cat has all CSS files already compressed.
Number of requests can be reduced by 20 (14%)
142
122
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roses. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
roses.cat
356 ms
www.roses.cat
854 ms
reset-cachekey-ec5891b42a7324d02c363552309cfd49.css
217 ms
base-cachekey-cddbab0c2ad00089c645b84999b829df.css
219 ms
columns.css
234 ms
authoring-cachekey-2dc5949b2371d12522570fff13f334d3.css
227 ms
++resource++plone.app.jquerytools.dateinput.css
231 ms
jqueryui.css
236 ms
resourcejquery-ui-themessunburst-patch-cachekey-99c00b4d69b84486ab4bd9db83b830e5.css
323 ms
resourceplonetheme.ajroses.stylesheetsmain-cachekey-ac53574a99b13b9ccdaf56fe88e192fc.css
328 ms
resourcejquery-ui-themessunburstjqueryui-cachekey-0238bd02c694ebf37630fb8c547c5679.css
342 ms
resourceplone.app.jquery-cachekey-0babf7f16cc8725e1cd03e1169587ac5.js
578 ms
resourcejquery-ui.min-cachekey-41c5adf7d1a39d3939b1116c612d4e31.js
710 ms
kss-bbb-cachekey-1083e1912dd3ee17fd301b5b19061d0a.js
429 ms
jquery.tools.min.js
663 ms
jquery.bxslider.min.js
454 ms
jquery.bxslider.css
457 ms
element.js
47 ms
ga.js
28 ms
5269520.jpg
332 ms
randomimage
805 ms
ombreta.png
147 ms
escut.png
148 ms
roses.png
532 ms
image
237 ms
image
149 ms
image
326 ms
image
342 ms
image
244 ms
image
467 ms
image
479 ms
image
761 ms
image
810 ms
image
581 ms
image
596 ms
image
893 ms
image
698 ms
image
712 ms
image
814 ms
image
830 ms
image
868 ms
image
912 ms
image
924 ms
image
928 ms
image
947 ms
image
977 ms
image
1001 ms
image
1023 ms
image
1038 ms
image
1041 ms
image
1064 ms
image
1083 ms
image
1108 ms
image
1136 ms
image
1154 ms
translateelement.css
57 ms
main.js
71 ms
image
1151 ms
__utm.gif
12 ms
element_main.js
54 ms
widgets.js
129 ms
sala_plens
1045 ms
image
1053 ms
image
1077 ms
translate_24dp.png
60 ms
l
39 ms
image
1020 ms
image
1034 ms
image
957 ms
image
965 ms
image
842 ms
image
856 ms
image
838 ms
image
809 ms
image
799 ms
image
722 ms
image
702 ms
image
685 ms
image
680 ms
image
696 ms
image
696 ms
image
694 ms
image
670 ms
image
660 ms
image
680 ms
e1cbbe71-6fc8-40f3-b497-adce6532015c.jpeg
695 ms
26bebb51-60fd-478b-ae04-a7261c91da3f.jpeg
696 ms
b161b52e-53ec-4e3e-9684-801d1c776be2.jpeg
683 ms
b12fc22f-78b2-49bd-aa56-01950313c00e.jpeg
676 ms
b323f428-f8b7-4dc0-9d6b-bc40f976354f.jpeg
657 ms
98685dac-e373-4fbb-9007-c9f18d6dcae4.jpeg
680 ms
f3e84c59-11e0-4faa-9b0f-4cd666129882.jpeg
695 ms
08a76fad-797c-4d51-9027-a633f79618e6.jpeg
698 ms
52c79c28-1580-4b06-87b5-4ba9ea233836.jpeg
676 ms
055844da-304a-465c-ad90-c82a2023f8e4.jpeg
686 ms
11.png
662 ms
NO.gif
681 ms
facebook_portada_icon.png
693 ms
flickr_portada_icon.png
697 ms
youtube_portada_icon.png
665 ms
pinterest_portada_icon.png
695 ms
image
662 ms
image
680 ms
image
688 ms
image
689 ms
image
672 ms
image
689 ms
image
678 ms
image
680 ms
image
681 ms
image
691 ms
image
676 ms
image
682 ms
image
682 ms
image
680 ms
image
675 ms
image
691 ms
image
684 ms
image
673 ms
image
692 ms
image
680 ms
transparent.png
665 ms
ombra.png
690 ms
cercador.png
689 ms
up.png
664 ms
down.png
698 ms
barra.png
678 ms
punt.png
660 ms
a2efd388-e65e-4cc2-bf17-b28d06f02663.jpeg
688 ms
9cce7659-1b27-413b-8b13-77d921bbcc4d.jpeg
685 ms
49b0e168-6c4b-4fe2-8da1-6ffc8596bc1f.jpeg
664 ms
370a9884-2ab7-4e70-b393-30c6186c636e.jpeg
693 ms
a6a303d8-827c-4b96-a421-f2bf273242b1.jpeg
679 ms
icon_rss.gif
654 ms
2e66d81a-bce8-40b7-a1b1-332e84321173.jpeg
686 ms
247996f2-8a65-451c-9d54-7aee473ed089.jpeg
688 ms
49865a70-8cf6-454a-878b-0dc7c0ea84a3.jpeg
666 ms
f111a43a-ddae-47cf-a805-c586cba5724c.jpeg
703 ms
da86de7f-a98c-4b1a-8002-a2ab0744106e.jpeg
679 ms
left.png
652 ms
right.png
678 ms
spinner.gif
687 ms
bx_loader.gif
674 ms
controls.png
704 ms
roses.cat 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Definition list items are not wrapped in <dl> elements
roses.cat best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
roses.cat 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
CA
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roses.cat can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Roses.cat 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.
roses.cat
Open Graph description is not detected on the main page of 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: