Tools & Wizards About Us
ovh.sn screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

ovh.sn

OVHcloud Sénégal : Cloud Computing & Hébergement Web

Page Load Speed

9.4 sec in total

First Response

342 ms

Resources Loaded

8.5 sec

Page Rendered

581 ms

ovh.sn screenshot

About Website

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

OVHcloud c'est plus de 80 services au meilleur ratio performance/prix, ouverts et réversibles : noms de domaine, vps, serveurs dédiés, cloud IaaS & PaaS

Visit ovh.sn

Key Findings

We analyzed Ovh.sn page load time and found that the first response time was 342 ms and then it took 9.1 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

ovh.sn performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value17,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

ovh.sn

342 ms

www.ovh.sn

326 ms

www.ovh.sn

1257 ms

bars.css

339 ms

share.css

344 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 76% of them (74 requests) were addressed to the original Ovh.sn, 21% (21 requests) were made to Ovh.com and 2% (2 requests) were made to Webanalytics2.ovh.net. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Ovh.sn.

Page Optimization Overview & Recommendations

Page size can be reduced by 770.0 kB (23%)

Content Size

3.4 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ovh.sn main page is 3.4 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. 30% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 139.2 kB

  • Original 164.6 kB
  • After minification 161.6 kB
  • After compression 25.4 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 139.2 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 132.7 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. Ovh images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 302.0 kB

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

CSS Optimization

-87%

Potential reduce by 196.1 kB

  • Original 226.0 kB
  • After minification 165.9 kB
  • After compression 29.9 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.sn needs all CSS files to be minified and compressed as it can save up to 196.1 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 83 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 12 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ovh.sn

ovh.sn

342 ms

www.ovh.sn

www.ovh.sn

326 ms

www.ovh.sn

www.ovh.sn

1257 ms

bars.css

bars.css

339 ms

share.css

share.css

344 ms

header.css

header.css

346 ms

footer.css

footer.css

355 ms

index.css

index.css

358 ms

fonts.css

fonts.css

599 ms

menu.css

menu.css

688 ms

patchSubs.css

patchSubs.css

694 ms

site-core.js

site-core.js

872 ms

site-more.js

site-more.js

893 ms

sessionAjax.js

sessionAjax.js

704 ms

ajax-lib-core.js

ajax-lib-core.js

935 ms

domainSuggest.js

domainSuggest.js

1034 ms

jquery.min.js

jquery.min.js

1253 ms

jquery.cookie.js

jquery.cookie.js

1050 ms

jquery.menu-aim.js

jquery.menu-aim.js

1221 ms

all_menu.js

all_menu.js

1219 ms

responsive.css

responsive.css

1284 ms

index.css

index.css

1415 ms

mediabox.js

mediabox.js

1436 ms

mediabox.css

mediabox.css

1501 ms

spriteCommunity.css

spriteCommunity.css

1469 ms

spriteWhyOVH.css

spriteWhyOVH.css

1472 ms

Senegal-icon.png

Senegal-icon.png

57 ms

United-States-of-Americ-icon.png

United-States-of-Americ-icon.png

55 ms

Canada-icon.png

Canada-icon.png

407 ms

Quebec-icon.png

Quebec-icon.png

389 ms

Latin-America-icon.png

Latin-America-icon.png

390 ms

Czech-Republic-icon.png

Czech-Republic-icon.png

436 ms

Germany-icon.png

Germany-icon.png

59 ms

Finland-icon.png

Finland-icon.png

57 ms

France-icon.png

France-icon.png

61 ms

Italy-icon.png

Italy-icon.png

61 ms

Ireland-icon.png

Ireland-icon.png

64 ms

Lithuania-icon.png

Lithuania-icon.png

63 ms

Netherlands-icon.png

Netherlands-icon.png

64 ms

Poland-icon.png

Poland-icon.png

65 ms

Portugal-icon.png

Portugal-icon.png

68 ms

Spain-icon.png

Spain-icon.png

67 ms

United-Kingdo-icon.png

United-Kingdo-icon.png

70 ms

Morocco-icon.png

Morocco-icon.png

71 ms

Tunisia-icon.png

Tunisia-icon.png

71 ms

worldIcon.png

worldIcon.png

71 ms

migration-email.png

migration-email.png

445 ms

logo-veeam-white.png

logo-veeam-white.png

556 ms

universe-wheel-ca.png

universe-wheel-ca.png

788 ms

jobs.jpg

jobs.jpg

804 ms

tw.png

tw.png

672 ms

fb.png

fb.png

676 ms

gPlus.png

gPlus.png

781 ms

logo.png

logo.png

903 ms

logo.png

logo.png

1009 ms

lato-regular-webfont.woff

lato-regular-webfont.woff

1035 ms

lato-light-webfont.woff

lato-light-webfont.woff

1152 ms

lato-hairline-webfont.woff

lato-hairline-webfont.woff

1130 ms

lato-bold-webfont.woff

lato-bold-webfont.woff

1186 ms

lato-black-webfont.woff

lato-black-webfont.woff

1799 ms

hebergementWeb.png

hebergementWeb.png

1763 ms

exchangeLarge.jpg

exchangeLarge.jpg

1650 ms

dotOvh.jpg

dotOvh.jpg

1534 ms

vps-2016-home.png

vps-2016-home.png

1829 ms

sdLarge.jpg

sdLarge.jpg

1643 ms

runLarge.jpg

runLarge.jpg

2060 ms

serveurInfra.jpg

serveurInfra.jpg

2110 ms

dedicatedLarge.jpg

dedicatedLarge.jpg

2435 ms

cdnDedicated.jpg

cdnDedicated.jpg

2311 ms

exchange-banner.png

exchange-banner.png

2361 ms

Cookbook.png

Cookbook.png

2815 ms

recap-semaine-ovh.png

recap-semaine-ovh.png

2372 ms

index.css

index.css

2416 ms

plus.png

plus.png

2621 ms

header-2.jpg

header-2.jpg

2712 ms

header.jpg

header.jpg

2710 ms

rwd-devices.jpg

rwd-devices.jpg

2727 ms

socialShare.png

socialShare.png

2847 ms

backup-veeam.png

backup-veeam.png

3359 ms

vRackWebinar.jpg

vRackWebinar.jpg

3206 ms

spriteCommunity.png

spriteCommunity.png

3136 ms

spriteWhyOVH.png

spriteWhyOVH.png

3844 ms

piwik.js

piwik.js

567 ms

smarttag-ovh.js

smarttag-ovh.js

370 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

3199 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

3124 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

3316 ms

sessionAjax.cgi

sessionAjax.cgi

3262 ms

spriteMenu.png

spriteMenu.png

3488 ms

dotOvh.jpg

dotOvh.jpg

3326 ms

dedicated.jpg

dedicated.jpg

3584 ms

cloud.jpg

cloud.jpg

3784 ms

piwik.php

piwik.php

107 ms

hit.xiti

hit.xiti

311 ms

recap-semaine-ovh.png

recap-semaine-ovh.png

1974 ms

header.jpg

header.jpg

1728 ms

header-2.jpg

header-2.jpg

2453 ms

rwd-devices.jpg

rwd-devices.jpg

2012 ms

Accessibility Review

ovh.sn accessibility score

74

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

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

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

Best Practices

ovh.sn 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

High

Missing source maps for large first-party JavaScript

SEO Factors

ovh.sn SEO score

91

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

ovh.sn

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: