Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 66

    SEO

    Google-friendlier than
    25% of websites

finanzasoaxaca.gob.mx

finanzas – Secretaría de Finanzas

Page Load Speed

3.2 sec in total

First Response

624 ms

Resources Loaded

2.4 sec

Page Rendered

195 ms

finanzasoaxaca.gob.mx screenshot

About Website

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

Portal de la Secretaría de Finanzas del Estado de Oaxaca

Visit finanzasoaxaca.gob.mx

Key Findings

We analyzed Finanzasoaxaca.gob.mx page load time and found that the first response time was 624 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

finanzasoaxaca.gob.mx performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value32.6 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

finanzasoaxaca.gob.mx

624 ms

jquery-2.1.1.js

880 ms

jquery-ui.js

1169 ms

bootstrap.js

587 ms

portal.js

293 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (47%)

Content Size

2.5 MB

After Optimization

1.3 MB

In fact, the total size of Finanzasoaxaca.gob.mx main page is 2.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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 42.5 kB

  • Original 49.1 kB
  • After minification 35.3 kB
  • After compression 6.6 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 13.8 kB, which is 28% 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 42.5 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 80.2 kB

  • Original 1.2 MB
  • After minification 1.1 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. Finanzas Oaxaca images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 776.5 kB

  • Original 924.6 kB
  • After minification 586.7 kB
  • After compression 148.1 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 776.5 kB or 84% of the original size.

CSS Optimization

-86%

Potential reduce by 252.0 kB

  • Original 293.8 kB
  • After minification 209.2 kB
  • After compression 41.8 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. Finanzasoaxaca.gob.mx needs all CSS files to be minified and compressed as it can save up to 252.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (29%)

Requests Now

52

After Optimization

37

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

Accessibility Review

finanzasoaxaca.gob.mx accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

finanzasoaxaca.gob.mx best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

finanzasoaxaca.gob.mx SEO score

66

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Finanzasoaxaca.gob.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Finanzasoaxaca.gob.mx 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 Finanzas 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: