Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

canalveo.com

Contenido nuestro - Canal Veo

Page Load Speed

8.9 sec in total

First Response

691 ms

Resources Loaded

7.2 sec

Page Rendered

1.1 sec

canalveo.com screenshot

About Website

Click here to check amazing Canal Veo content. Otherwise, check out these important facts you probably never knew about canalveo.com

Visit canalveo.com

Key Findings

We analyzed Canalveo.com page load time and found that the first response time was 691 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

canalveo.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

canalveo.com

691 ms

canalveo.com

1978 ms

bootstrap.min.css

66 ms

custom.css

347 ms

custom.scss

515 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 70% of them (72 requests) were addressed to the original Canalveo.com, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Canalveo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.1 kB (7%)

Content Size

5.1 MB

After Optimization

4.7 MB

In fact, the total size of Canalveo.com main page is 5.1 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. 75% 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 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 114.6 kB

  • Original 137.6 kB
  • After minification 117.5 kB
  • After compression 23.1 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 20.2 kB, which is 15% 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 114.6 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 209.0 kB

  • Original 4.2 MB
  • After minification 4.0 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. Canal Veo images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 9.2 kB

  • Original 577.6 kB
  • After minification 577.6 kB
  • After compression 568.4 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

-9%

Potential reduce by 9.4 kB

  • Original 100.7 kB
  • After minification 100.7 kB
  • After compression 91.3 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. Canalveo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (42%)

Requests Now

83

After Optimization

48

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

Accessibility Review

canalveo.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

canalveo.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

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

canalveo.com SEO score

79

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

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

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Canalveo.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Canalveo.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Canal Veo. 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: