Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

reporteindigo.com

Reporte Indigo - Reporte Índigo se publica de lunes a viernes en la CDMX, Guadalajara y Monterrey. Noticias, entrevistas, opinión, videos

Page Load Speed

2.7 sec in total

First Response

19 ms

Resources Loaded

2.3 sec

Page Rendered

374 ms

reporteindigo.com screenshot

About Website

Visit reporteindigo.com now to see the best up-to-date Reporte Indigo content for Mexico and also check out these interesting facts you probably never knew about reporteindigo.com

Reporte Índigo se publica de lunes a viernes en la CDMX, Guadalajara y Monterrey. Noticias, entrevistas, opinión, videos.

Visit reporteindigo.com

Key Findings

We analyzed Reporteindigo.com page load time and found that the first response time was 19 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

reporteindigo.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value2,220 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

reporteindigo.com

19 ms

type.css

5 ms

css_0b14602d6f6c936ddc897a426cc6009a_3110.css

48 ms

js_09e907a53e6a731628ef9ec9d9afd79d_3110.js

67 ms

thickbox_engine.js

46 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 9% of them (16 requests) were addressed to the original Reporteindigo.com, 34% (61 requests) were made to Df3vgdkto12gv.cloudfront.net and 16% (29 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (645 ms) relates to the external source External.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.0 MB (48%)

Content Size

8.4 MB

After Optimization

4.4 MB

In fact, the total size of Reporteindigo.com main page is 8.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. 85% 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. Javascripts take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 98.5 kB

  • Original 116.2 kB
  • After minification 107.1 kB
  • After compression 17.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. 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 98.5 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 51.1 kB

  • Original 3.6 MB
  • After minification 3.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. Reporte Indigo images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 3.4 MB

  • Original 4.1 MB
  • After minification 3.0 MB
  • After compression 774.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.4 MB or 81% of the original size.

CSS Optimization

-84%

Potential reduce by 507.0 kB

  • Original 605.2 kB
  • After minification 591.7 kB
  • After compression 98.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. Reporteindigo.com needs all CSS files to be minified and compressed as it can save up to 507.0 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

174

After Optimization

107

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

Accessibility Review

reporteindigo.com accessibility score

91

Accessibility Issues

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

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.

Best Practices

reporteindigo.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

reporteindigo.com SEO score

98

Search Engine Optimization Advices

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 Reporteindigo.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 Reporteindigo.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 Reporte Indigo. 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: