Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ivi.es

Clínicas de Reproducción asistida - Tratamientos de fertilidad - IVI

Page Load Speed

3.7 sec in total

First Response

198 ms

Resources Loaded

3.4 sec

Page Rendered

139 ms

ivi.es screenshot

About Website

Welcome to ivi.es homepage info - get ready to check IVI best content for Spain right away, or after learning these important things about ivi.es

En IVI somos especialistas en técnicas de reproducción asistida desarrolladas para combatir la infertilidad de hombres y mujeres y ayudar a tener hijos.

Visit ivi.es

Key Findings

We analyzed Ivi.es page load time and found that the first response time was 198 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ivi.es performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value7.2 s

31/100

10%

TBT (Total Blocking Time)

Value2,320 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

ivi.es

198 ms

ivi.es

394 ms

www.ivi.es

592 ms

bootstrap-pacientes.css

778 ms

prehome.css

402 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 60% of them (28 requests) were addressed to the original Ivi.es, 9% (4 requests) were made to Google-analytics.com and 4% (2 requests) were made to Ivi-fertility.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ivi.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 653.7 kB (66%)

Content Size

989.1 kB

After Optimization

335.5 kB

In fact, the total size of Ivi.es main page is 989.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 606.5 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 11.7 kB

  • Original 17.7 kB
  • After minification 17.4 kB
  • After compression 6.0 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 11.7 kB or 66% of the original size.

Image Optimization

-24%

Potential reduce by 45.8 kB

  • Original 191.7 kB
  • After minification 145.9 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, IVI needs image optimization as it can save up to 45.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 452.0 kB

  • Original 606.5 kB
  • After minification 465.5 kB
  • After compression 154.5 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 452.0 kB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 144.2 kB

  • Original 173.2 kB
  • After minification 163.2 kB
  • After compression 29.0 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. Ivi.es needs all CSS files to be minified and compressed as it can save up to 144.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (67%)

Requests Now

39

After Optimization

13

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

Accessibility Review

ivi.es accessibility score

67

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Form elements do not have associated labels

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>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ivi.es best practices score

85

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ivi.es SEO score

82

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

High

Tap targets are not sized appropriately

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 Ivi.es 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 Ivi.es 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 IVI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: