3.5 sec in total
160 ms
2.8 sec
591 ms
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.ptWe 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 60% of websites can load faster.
ovh.pt performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value4.3 s
41/100
25%
Value4.5 s
73/100
10%
Value1,010 ms
27/100
30%
Value0.052
99/100
15%
Value9.8 s
28/100
10%
160 ms
163 ms
201 ms
31 ms
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 size can be reduced by 617.8 kB (34%)
1.8 MB
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.
Potential reduce by 472.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. 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.
Potential reduce by 106.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.
Potential reduce by 14.8 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.
Potential reduce by 24.2 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.2 kB or 16% of the original size.
Number of requests can be reduced by 76 (70%)
108
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.
ovh.pt
160 ms
www.ovh.pt
163 ms
201 ms
homepage_ovhcloud.css
31 ms
ovh_abt.js
334 ms
sentry-legacy.min.js
51 ms
js_5QicyAWaOeclijIkiKqySfPxEFFZtqL5Pi2aIJmFbDU.js
148 ms
ods-menu-highlight.min.js
135 ms
ods-menu-highlight-legacy.min.js
163 ms
ods-header.min.js
162 ms
ods-header-legacy.min.js
162 ms
js_YpGqPSGe50ZFzWCoxbzGMNpL2Y9zz62A_jT25wrMTUY.js
162 ms
passive-event-listeners.min.js
166 ms
passive-event-listeners-legacy.min.js
165 ms
i18n.min.js
178 ms
browser-back-flush-cache.min.js
178 ms
browser-back-flush-cache-legacy.min.js
178 ms
local-anchors.min.js
179 ms
local-anchors-legacy.min.js
182 ms
oui-back-to-top.min.js
183 ms
oui-back-to-top-legacy.min.js
194 ms
js_cx2pXj6T5Q5FlVPuRLO-m64p-7xoaotYGGIlg7VAQVY.js
196 ms
ods-fitty.min.js
194 ms
ods-fitty-legacy.min.js
195 ms
js_7qsJpk4_FDbjBoIJ7WYIfqTJrcUhYtb0zbYS-r5um9Y.js
199 ms
analyticsSelfPromotion.min.js
200 ms
js_q2ChBsm3FnbvVLtLOpzhuw6HmvYoUHC1zkxFxUu367I.js
209 ms
ovh_delta.js
304 ms
ovh_tags.js
379 ms
ods-olu.min.js
211 ms
ods-olu-legacy.min.js
212 ms
ods-footer.min.js
213 ms
ods-footer-legacy.min.js
216 ms
webcallback-federation.min.js
215 ms
webcallback-federation-legacy.min.js
226 ms
ods-background-video.min.js
228 ms
ods-background-video-legacy.min.js
228 ms
odss-section-background-media-lazyload.min.js
230 ms
odss-section-background-media-lazyload-legacy.min.js
300 ms
osds-icon.esm.js
301 ms
odss-slider.min.js
303 ms
odss-slider-legacy.min.js
302 ms
js_J6XH5FuXlIfVm1sK95WgchMie5p2_X4he4FBh3u_b88.js
288 ms
optiextension.dll
546 ms
ovh_domain_form.min.js
178 ms
ovh_domain_form-legacy.min.js
177 ms
local-search-category-mapping.min.js
152 ms
local-search-category-mapping-legacy.min.js
150 ms
js_4Z0jeQ4Ez80cuVZ2ICq5uuS-66EnmajtOrmAvlUCKBA.js
151 ms
algolia-search.min.js
154 ms
algolia-search-legacy.min.js
150 ms
ods-search-bar.min.js
150 ms
ods-search-bar-legacy.min.js
149 ms
languages-switcher.min.js
139 ms
ods-skip-link.min.js
139 ms
ods-skip-link-legacy.min.js
139 ms
source-sans-pro-all-400-normal.woff
148 ms
source-sans-pro-all-300-normal.woff
200 ms
source-sans-pro-all-600-normal.woff
202 ms
source-sans-pro-all-700-normal.woff
187 ms
pt-pt.svg
124 ms
de.svg
183 ms
es.svg
186 ms
fr.svg
185 ms
en-ie.svg
186 ms
it.svg
176 ms
nl.svg
176 ms
pl.svg
176 ms
en-gb.svg
178 ms
en-ca.svg
173 ms
fr-ca.svg
174 ms
en-us.svg
167 ms
es-419.svg
163 ms
fr-ma.svg
166 ms
fr-sn.svg
167 ms
fr-tn.svg
94 ms
en-au.svg
95 ms
en-sg.svg
100 ms
en-142.svg
95 ms
en-in.svg
95 ms
world.svg
92 ms
Website_Logo_700x400_Portuguese_0.png
97 ms
ecx-3005-vps-promo_350x350.png
174 ms
sd-scale_white_background2x_1.png
175 ms
multiyear600.png
175 ms
SD.png
175 ms
enterprise_0.png
173 ms
public%20cloud.png
170 ms
Web.png
173 ms
auchan.png
171 ms
MACOPHARMA-LOGO.png
172 ms
logo-societe-generale_1.png
172 ms
Louis-Vuitton-Logo-3-600x600_1.jpg
165 ms
icons.woff
164 ms
Irontec_logo_1.png
112 ms
sopra-steria.png
111 ms
Capgemini_Logo_2COL_RGB_1_0.png
110 ms
network-map_bandeauhp.png
111 ms
libro-de-reclamacoes-pt-s.png
109 ms
x.svg
109 ms
linkedin.svg
108 ms
facebook.svg
109 ms
youtube.svg
109 ms
twitch.svg
109 ms
discord.svg
110 ms
blog.svg
109 ms
github.svg
106 ms
css_saG2SfeHlJ5hQAGLv7lwLf-wG1cQB7JBoIdN3zohRXs.css
20 ms
css_kIIbkinlFMDN0PwtnC7bn0oKU6LmLaOBBmggwCi353c.css
57 ms
survey.dll
474 ms
style_form_newsletter_footer.css
79 ms
jquery-3.1.1.min.js
461 ms
bootstrap-datetimepicker.min.js
459 ms
standalone-datetimepicker.css
459 ms
bootstrap-datetimepicker.pt.js
870 ms
SIM_SurveyManagerResponsive.min.js
457 ms
icons.woff
23 ms
source-sans-pro-all-400-italic.woff
385 ms
ovh_external.js
130 ms
ovh.pt accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
[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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ovh.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ovh.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
PT
PT
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.
ovh.pt
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: