Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

roses.cat

Ajuntament de Roses

Page Load Speed

5.3 sec in total

First Response

356 ms

Resources Loaded

4.6 sec

Page Rendered

332 ms

About Website

Click here to check amazing Roses content for Spain. Otherwise, check out these important facts you probably never knew about roses.cat

Visit roses.cat

Key Findings

We 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.

Performance Metrics

roses.cat performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value5,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 277.9 kB (16%)

Content Size

1.7 MB

After Optimization

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.

HTML Optimization

-86%

Potential reduce by 73.0 kB

  • Original 85.4 kB
  • After minification 58.5 kB
  • After compression 12.3 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.

Image Optimization

-8%

Potential reduce by 111.6 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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.

JavaScript Optimization

-39%

Potential reduce by 93.2 kB

  • Original 241.9 kB
  • After minification 241.9 kB
  • After compression 148.7 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.

CSS Optimization

-2%

Potential reduce by 70 B

  • Original 3.6 kB
  • After minification 3.6 kB
  • After compression 3.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. Roses.cat has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (14%)

Requests Now

142

After Optimization

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.

Accessibility Review

roses.cat accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

High

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

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

Definition list items are not wrapped in <dl> elements

Best Practices

roses.cat best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Page has valid source maps

SEO Factors

roses.cat SEO score

84

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    CA

  • Language Claimed

    CA

  • Encoding

    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.

Social Sharing Optimization

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: