Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

oaxaca.gob.mx

Gobierno del Estado de Oaxaca

Page Load Speed

718 ms in total

First Response

300 ms

Resources Loaded

303 ms

Page Rendered

115 ms

oaxaca.gob.mx screenshot

About Website

Visit oaxaca.gob.mx now to see the best up-to-date Oaxaca content for Mexico and also check out these interesting facts you probably never knew about oaxaca.gob.mx

Gobierno del Estado de Oaxaca

Visit oaxaca.gob.mx

Key Findings

We analyzed Oaxaca.gob.mx page load time and found that the first response time was 300 ms and then it took 418 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

oaxaca.gob.mx performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.3 s

0/100

25%

SI (Speed Index)

Value32.9 s

0/100

10%

TBT (Total Blocking Time)

Value51,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value76.2 s

0/100

10%

Network Requests Diagram

oaxaca.gob.mx

300 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Oaxaca.gob.mx and no external sources were called. The less responsive or slowest element that took the longest time to load (300 ms) belongs to the original domain Oaxaca.gob.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 19 B (18%)

Content Size

106 B

After Optimization

87 B

In fact, the total size of Oaxaca.gob.mx main page is 106 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 106 B which makes up the majority of the site volume.

HTML Optimization

-18%

Potential reduce by 19 B

  • Original 106 B
  • After minification 94 B
  • After compression 87 B

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 12 B, which is 11% 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 19 B or 18% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

oaxaca.gob.mx accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

oaxaca.gob.mx best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

oaxaca.gob.mx SEO score

75

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    ES

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oaxaca.gob.mx 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 Oaxaca.gob.mx main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Oaxaca. 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: