Sat.gob.mx Site Title

Portal de trámites y servicios - SAT

Sat.gob.mx Meta Description

Portal de trámites y servicios sat

Sat.gob.mx Test Results

Sat.gob.mx Mobile Performance: 44/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 4,010 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Serve images in next-gen formats. Potential savings of 318 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Avoid multiple page redirects. Potential savings of 1,410 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Properly size images. Potential savings of 267 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused JavaScript. Potential savings of 125 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Efficiently encode images. Potential savings of 99 KiB
Optimized images load faster and consume less cellular data. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Serve static assets with an efficient cache policy
50 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid chaining critical requests
31 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
54 requests • 1,297 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Sat.gob.mx Mobile SEO: 76/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more. Lighthouse was unable to download a robots.txt file
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
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.
Tap targets are not sized appropriately
97% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Sat.gob.mx Mobile Best Practices: 69/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Sat.gob.mx Mobile Progressive Web App: 43/100
Quick overview:
PWA Optimized
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 362px does not match the window size of 360px.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Sat.gob.mx Mobile Accessibility: 80/100
Quick overview:
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Similar tests
www.sat.com
www.sat.net
www.sat.org
www.sat.info
www.sat.biz
www.sat.us
www.sat.mobi
www.at.gob.mx
www.sat.gob.mx
www.wat.gob.mx
www.swat.gob.mx
www.wsat.gob.mx
www.eat.gob.mx
www.seat.gob.mx
www.esat.gob.mx
www.dat.gob.mx
www.sdat.gob.mx
www.dsat.gob.mx
www.zat.gob.mx
www.szat.gob.mx
www.zsat.gob.mx
www.xat.gob.mx
www.sxat.gob.mx
www.xsat.gob.mx
www.aat.gob.mx
www.saat.gob.mx
www.asat.gob.mx
www.st.gob.mx
www.sqt.gob.mx
www.saqt.gob.mx
www.sqat.gob.mx
www.swt.gob.mx
www.sawt.gob.mx
www.sst.gob.mx
www.sast.gob.mx
www.ssat.gob.mx
www.szt.gob.mx
www.sazt.gob.mx
www.sa.gob.mx
www.sar.gob.mx
www.satr.gob.mx
www.sart.gob.mx
www.saf.gob.mx
www.satf.gob.mx
www.saft.gob.mx
www.sag.gob.mx
www.satg.gob.mx
www.sagt.gob.mx
www.say.gob.mx
www.saty.gob.mx
www.sayt.gob.mx
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.