Access pronto.es. Pronto - Revista de prensa rosa y noticias del corazón

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value3,760 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

pronto.es

12 ms

www.pronto.es

451 ms

screen.css

12 ms

home-color.css

302 ms

css2

40 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Pronto.es, 41% (35 requests) were made to Imagenes.pronto.es and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (637 ms) relates to the external source Imagenes.pronto.es.

Content Size

4.5 MB

After Optimization

3.9 MB

In fact, the total size of Pronto.es main page is 4.5 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. 80% 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 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 155.5 kB

Original 179.2 kB
After minification 138.6 kB
After compression 23.7 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 40.5 kB, which is 23% 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 155.5 kB or 87% of the original size.

Image Optimization

-11%

Potential reduce by 478.7 kB

Original 4.2 MB
After minification 3.8 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. Obviously, Pronto needs image optimization as it can save up to 478.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 87 B

Original 50.3 kB
After minification 50.3 kB
After compression 50.2 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

-27%

Potential reduce by 5.6 kB

Original 21.2 kB
After minification 21.2 kB
After compression 15.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. Pronto.es needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 27% of the original size.

Requests Now

After Optimization

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

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

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.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

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

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ES
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pronto.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pronto.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

pronto.es

Open Graph data is detected on the main page of Pronto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Pronto - Revista de prensa rosa y noticias del corazón

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

pronto.es

www.pronto.es

screen.css

home-color.css

css2

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

pronto.es

www.pronto.es

screen.css

home-color.css

css2

home.bundle.js

js

loader.js

desktop-mobile.min.js

fbevents.js

gtm.js

gtm.js

64005797da76a.png

66aa6b4d20cb9.r_d.956-422-0.jpeg

66747d96d2ddf.webp

66aa469a852f1.r_d.526-442-10210.png

6687a3f8ce91f.webp

667d6087684b5.r_d.600-435-0.webp

62aaafa4144c3.jpeg

66a7a9fa6999f.r_d.542-780-0.webp

655f6778f2672.webp

66544d49b235f.r_d.600-456-0.webp

66570d1e0d4fa.r_d.600-424-0.webp

66696c444954d.webp

65d5e0076c161.r_d.528-759-10000.webp

66869b1f0924d.r_d.600-401-0.webp

668ba08b4f439.r_d.704-1093-5626.webp

668651a6892d1.r_d.651-172-0.webp

6686586c8bc9b.r_d.600-316-0.webp

668eb3bd343f4.r_d.644-558-0.webp

644a722c43db3.webp

64aed6a7230c1.r_d.1236-1330-0.webp

6674016dd6dea.r_d.722-626-0.webp

62cc07d1aa07f.jpeg

663a38df41d5c.r_d.650-433-0.webp

663a0ad71af1e.r_d.694-464-0.webp

66339d5a6a054.webp

669f9ec77b0b3.r_d.591-471-0.webp

6699213f5ed50.r_d.603-542-0.webp

668e56cf1edf6.r_d.600-410-0.webp

668f845a3c1f1.r_d.877-493-0.webp

66827ec496897.r_d.600-419-0.webp

66a22721a511e.r_d.588-422-0.webp