Access ontinet.com. INICIO

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value23.3 s

0/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

ontinet.com

202 ms

ontinet.com

436 ms

web.assets_frontend.min.css

477 ms

web.assets_frontend_minimal.min.js

293 ms

script.js

20379 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 71% of them (15 requests) were addressed to the original Ontinet.com, 14% (3 requests) were made to Fonts.gstatic.com and 10% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Plausible.protegerse.com.

Content Size

1.4 MB

After Optimization

1.3 MB

In fact, the total size of Ontinet.com main page is 1.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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.8 kB

Original 36.2 kB
After minification 26.4 kB
After compression 7.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. This page needs HTML code to be minified as it can gain 9.8 kB, which is 27% 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 28.8 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 123.4 kB

Original 1.4 MB
After minification 1.3 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. ONTINET images are well optimized though.

Requests Now

After Optimization

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ONTINET. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

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

High

Document doesn't use 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 Ontinet.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 Ontinet.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 ONTINET. 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: