Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

dbalears.cat

dBalears

Page Load Speed

10.8 sec in total

First Response

308 ms

Resources Loaded

7.6 sec

Page Rendered

2.9 sec

dbalears.cat screenshot

About Website

Welcome to dbalears.cat homepage info - get ready to check DBalears best content for Spain right away, or after learning these important things about dbalears.cat

dBalears

Visit dbalears.cat

Key Findings

We analyzed Dbalears.cat page load time and found that the first response time was 308 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dbalears.cat performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value6,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

dbalears.cat

308 ms

dbalears.cat

451 ms

www.dbalears.cat

898 ms

loader.js

924 ms

bootstrap.min.css

101 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Dbalears.cat, 71% (69 requests) were made to Db.gsstatic.es and 8% (8 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Db.gsstatic.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.0 kB (15%)

Content Size

3.3 MB

After Optimization

2.8 MB

In fact, the total size of Dbalears.cat main page is 3.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 343.2 kB

  • Original 391.8 kB
  • After minification 364.1 kB
  • After compression 48.5 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 343.2 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 153.4 kB

  • Original 2.6 MB
  • After minification 2.5 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. DBalears images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.2 kB

  • Original 236.5 kB
  • After minification 235.8 kB
  • After compression 227.3 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.

CSS Optimization

-0%

Potential reduce by 124 B

  • Original 29.8 kB
  • After minification 29.8 kB
  • After compression 29.7 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. Dbalears.cat has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (28%)

Requests Now

92

After Optimization

66

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DBalears. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

dbalears.cat accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

dbalears.cat best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

dbalears.cat SEO score

75

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Dbalears.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 Dbalears.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 DBalears. 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: