Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ovh.pt

OVHcloud Portugal: Cloud Computing e Alojamento Web

Page Load Speed

3.5 sec in total

First Response

160 ms

Resources Loaded

2.8 sec

Page Rendered

591 ms

ovh.pt screenshot

About Website

Welcome to ovh.pt homepage info - get ready to check Ovh best content for Brazil right away, or after learning these important things about ovh.pt

A OVHcloud oferece mais de 80 serviços, abertos e reversíveis, com a melhor relação preço/desempenho: domínios, VPS, servidores dedicados, cloud IaaS e PaaS.

Visit ovh.pt

Key Findings

We analyzed Ovh.pt page load time and found that the first response time was 160 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ovh.pt performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

ovh.pt

160 ms

www.ovh.pt

163 ms

201 ms

homepage_ovhcloud.css

31 ms

ovh_abt.js

334 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ovh.pt, 88% (105 requests) were made to Ovhcloud.com and 7% (8 requests) were made to Ovh.slgnt.eu. The less responsive or slowest element that took the longest time to load (870 ms) relates to the external source Ovh.slgnt.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.6 kB (34%)

Content Size

1.8 MB

After Optimization

1.2 MB

In fact, the total size of Ovh.pt main page is 1.8 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 729.6 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 472.5 kB

  • Original 517.8 kB
  • After minification 395.1 kB
  • After compression 45.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 122.7 kB, which is 24% 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 472.5 kB or 91% of the original size.

Image Optimization

-15%

Potential reduce by 106.3 kB

  • Original 729.6 kB
  • After minification 623.3 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. Obviously, Ovh needs image optimization as it can save up to 106.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 14.5 kB

  • Original 430.5 kB
  • After minification 430.5 kB
  • After compression 416.1 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

-16%

Potential reduce by 24.3 kB

  • Original 148.9 kB
  • After minification 148.9 kB
  • After compression 124.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. Ovh.pt needs all CSS files to be minified and compressed as it can save up to 24.3 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (70%)

Requests Now

108

After Optimization

32

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

Accessibility Review

ovh.pt accessibility score

65

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

[aria-*] attributes are not valid or misspelled

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

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.

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

ovh.pt best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ovh.pt SEO score

92

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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