Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

bitassa.cat

Benjamí Villoslada, bitòleg tecnooptimista

Page Load Speed

17.7 sec in total

First Response

109 ms

Resources Loaded

17.3 sec

Page Rendered

263 ms

bitassa.cat screenshot

About Website

Visit bitassa.cat now to see the best up-to-date Bitassa content and also check out these interesting facts you probably never knew about bitassa.cat

Treballo acompanyant organitzacions en la seva immersió digital. Ho faig com a CTO compartit, analista digital i divulgador.

Visit bitassa.cat

Key Findings

We analyzed Bitassa.cat page load time and found that the first response time was 109 ms and then it took 17.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

bitassa.cat performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

bitassa.cat

109 ms

flavors.me

223 ms

324798285.js

11 ms

KievitPro-Book.css

88 ms

Din-Medium.css

176 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Bitassa.cat, 63% (34 requests) were made to Flavors.me and 24% (13 requests) were made to Static.flavors.me. The less responsive or slowest element that took the longest time to load (990 ms) relates to the external source Static.flavors.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.7 kB (18%)

Content Size

1.6 MB

After Optimization

1.3 MB

In fact, the total size of Bitassa.cat main page is 1.6 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.

HTML Optimization

-81%

Potential reduce by 16.2 kB

  • Original 20.1 kB
  • After minification 17.5 kB
  • After compression 3.9 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 2.6 kB, which is 13% 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 16.2 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 31.5 kB

  • Original 1.2 MB
  • After minification 1.2 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. Bitassa images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 221.1 kB

  • Original 352.7 kB
  • After minification 352.7 kB
  • After compression 131.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 221.1 kB or 63% of the original size.

CSS Optimization

-76%

Potential reduce by 14.9 kB

  • Original 19.5 kB
  • After minification 19.2 kB
  • After compression 4.6 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. Bitassa.cat needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (17%)

Requests Now

52

After Optimization

43

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

Accessibility Review

bitassa.cat accessibility score

100

Accessibility Issues

Best Practices

bitassa.cat best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

bitassa.cat SEO score

93

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

Language and Encoding

  • Language Detected

    CA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bitassa.cat can be misinterpreted by Google and other search engines. Our service has detected that Catalan 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 Bitassa.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 data is detected on the main page of Bitassa. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: