Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

sat.gob.mx

sat.gob.mx is SSL secured

Free website and domain report on sat.gob.mx

Last Updated: 16th May, 2023 Update Now
Overview

Snoop Summary for sat.gob.mx

This is a free and comprehensive report about sat.gob.mx. Sat.gob.mx is hosted in Mexico on a server with an IP address of 200.33.84.233, where MXN is the local currency and the local language is Spanish. Sat.gob.mx is expected to earn an estimated $23,691 USD per day from advertising revenue. The sale of sat.gob.mx would possibly be worth $17,294,804 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Sat.gob.mx is unbelievably popular with an estimated 2,544,499 daily unique visitors. This report was last updated 16th May, 2023.

About sat.gob.mx

Site Preview: sat.gob.mx sat.gob.mx
Title: Portal de trámites y servicios - SAT
Description: Portal de trámites y servicios sat
Keywords and Tags: buzon tributario, government, military, mis cuentas, popular, rfc con curp, rfc mexico, rfc sat, sacar rfc, sat citas, sat declaracion, sat gob, sat gob mx, sat mexico, sat mis cuentas, sat tramites, servicio de administracion tributaria, www sat gob mx
Related Terms: agencia virtual sat, portal sat, portal sat guatemala, sat de guatemala, sat en linea, sat gob gt, sat guatemala, sat score range, sat vocabulary, www sat gob gt
Fav Icon:
Age: Over 26 years old
Domain Created: 18th February, 1998
Domain Updated: 18th February, 2022
Domain Expires: 17th February, 2023
Review

Snoop Score

5/5 (Perfect!)

Valuation

$17,294,804 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 987
Alexa Reach: 0.0467%
SEMrush Rank (US): 19,157
SEMrush Authority Score: 67
Moz Domain Authority: 80
Moz Page Authority: 54

Rank By Country

Country Alexa Rank
Mexico Flag Mexico 17
United States Flag United States 1,859

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 29,826 0
Traffic: 131,359 0
Cost: $19,258 USD $0 USD
Traffic

Visitors

Daily Visitors: 2,544,499
Monthly Visitors: 77,446,534
Yearly Visitors: 928,742,135
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Mexico Flag Mexico Daily: 2,297,683
Monthly: 69,934,220
Yearly: 838,654,148 		90.3%
Other Daily: 27,989
Monthly: 851,912
Yearly: 10,216,163 		1.1%
United States Flag United States Daily: 218,827
Monthly: 6,660,402
Yearly: 79,871,824 		8.6%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $23,691 USD
Monthly Revenue: $721,095 USD
Yearly Revenue: $8,647,397 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Mexico Flag Mexico Daily: $2,655 USD
Monthly: $80,817 USD
Yearly: $969,162 USD 		11.2%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD 		<0.1%
United States Flag United States Daily: $21,036 USD
Monthly: $640,278 USD
Yearly: $7,678,236 USD 		88.8%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 1,429,152
Referring Domains: 8,725
Referring IPs: 8,887
Sat.gob.mx has 1,429,152 backlinks according to SEMrush. 76% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve sat.gob.mx's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of sat.gob.mx's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://tmclegal.com/news/page/3/
Target: http://omawww.sat.gob.mx/aduanasPortal/Paginas/index.html#!/mupea
2
Source: https://tmclegal.com/category/non-classe/page/3/
Target: http://omawww.sat.gob.mx/aduanasPortal/Paginas/index.html#!/mupea
3
Source: http://www.masfacturas.mx/facturacion-electronica.aspx?D=mWKcbw4eCZvDiP7u3vNF8w%3D%3D
Target: https://citas.sat.gob.mx/citasat/home.aspx
4
Source: http://www.masfacturas.mx/facturacion-electronica.aspx?D=mWKcbw4eCZvDiP7u3vNF8w%3D%3D
Target: https://www.sat.gob.mx/tramites/17507/envia-la-solicitud-para-tu-certificado-de-sello-digital-para-emitir-facturas-electronicas
5
Source: https://www.masfacturas.mx/facturacion-electronica.aspx?D=AxrFu8BuNushGPDj2cb5gg%3D%3D
Target: https://citas.sat.gob.mx/citasat/home.aspx

Top Ranking Keywords (US)

1
Keyword: sat mexico
Ranked Page: https://www.sat.gob.mx/
2
Keyword: mis cuentas
Ranked Page: https://rfs.siat.sat.gob.mx/
3
Keyword: sat gob mx
Ranked Page: https://www.sat.gob.mx/
4
Keyword: sat gob
Ranked Page: https://www.sat.gob.mx/
5
Keyword: www sat gob mx
Ranked Page: https://www.sat.gob.mx/

Domain Analysis

Value Length
Domain: sat.gob.mx 10
Domain Name: sat 3
Extension (TLD): gobmx 5
Expiry Check:

Page Speed Analysis

Average Load Time: 1.24 seconds
Load Time Comparison: Faster than 62% of sites

PageSpeed Insights

Avg. (All Categories) 71
Performance 90
Accessibility 88
Best Practices 83
SEO 73
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.sat.gob.mx/home
Updated: 18th April, 2022

1.24 seconds
First Contentful Paint (FCP)
84%
8%
8%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
90

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for sat.gob.mx. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.007
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://sat.gob.mx/
http/1.1
0
140.19900001585
543
0
302
text/html
https://wwwmat.sat.gob.mx/
http/1.1
140.45900001656
660.29999998864
568
0
302
text/html
https://www.sat.gob.mx/home
h2
660.66399996635
1080.7250000071
17537
88706
200
text/html
Document
https://www.sat.gob.mx/satys/css/all.css?1.1
h2
1094.0120000159
1371.4470000705
786
265
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/js/jquery.js
h2
1094.345999998
1252.7710000286
33953
95933
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
h2
1094.6610000683
1190.0039999746
64513
240439
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/datatables.js
h2
1095.0960000046
1247.3110000137
27702
79615
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/datatables.responsive.js
h2
1095.604000031
1315.8730000723
8781
25594
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/swipe.js
h2
1095.854000072
1245.6030000467
4574
15252
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/jsp.js
h2
1096.0429999977
1267.1110000229
5443
14114
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/main.js
h2
1096.2360000703
1245.1280000387
6616
24833
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/owl.carousel.min.js
h2
1096.9990000594
1283.0270000268
11150
40402
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/hammer.min.js
h2
1097.1630000276
1385.6500000693
7077
18327
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/sequence.min.js
h2
1097.6080000401
1401.3869999908
12833
48192
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
h2
1097.8420000756
1259.0680000139
25108
137831
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/entrada/sliderengine/initslider-1.js
h2
1098.1020000763
1467.9539999925
2464
6757
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/moment.min.js
h2
1098.4080000781
1444.8290000437
12542
34743
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/css/fullcalendar.min.css
h2
1098.8249999937
1399.1350000724
3559
12100
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
h2
1099.2010000627
1420.3550000675
28646
94722
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/es.js
h2
1099.4949999731
1397.5830000127
1743
2234
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/css/owl.carousel.css
h2
1099.6770000784
1227.7839999879
1762
4830
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/img/logo3.png
h2
1650.1830000198
1748.309000046
18950
18343
200
image/png
Image
https://www.sat.gob.mx/satys/img/menu_search.png
h2
1650.7500000298
1724.9160000356
1012
406
200
image/png
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
h2
1729.5220000669
1972.4970000098
100058
99280
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
h2
1730.0340000074
1884.056000039
115311
114552
200
image/png
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
h2
1730.2840000484
2076.4480000362
41564
40906
200
image/png
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
h2
1731.0000000289
1924.1110000294
31766
30984
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
h2
1731.1670000199
1797.2030000528
81634
80862
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
h2
1731.5630000085
2088.9540000353
67076
66303
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
h2
1732.0319999708
1774.9980000081
22211
21512
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
h2
1734.075000044
2199.8790000798
144145
143359
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
h2
1735.1679999847
1797.6999999955
26257
25554
200
image/jpeg
Image
https://www.sat.gob.mx/satys/img/social_buttons.jpg
h2
1735.3170000715
2213.9100000495
25155
24547
200
image/jpeg
Image
https://www.sat.gob.mx/satys/css/style.css?1.2
h2
1372.9199999943
1471.0729999933
9854
50940
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/sidebar.css?1.2
h2
1373.2040000614
1389.4060000312
1881
4893
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/media_queries.css
h2
1373.4870000044
1649.459999986
6275
27172
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/datatables.css
h2
1374.2080000229
1451.7680000281
3094
17940
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/datatables.responsive.css
h2
1374.3999999715
1460.3310000384
1288
3157
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.css
h2
1374.5820000768
1624.8159999959
7957
30203
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/slider.css
h2
1374.7440000298
1461.3580000587
1876
6906
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/jsp.css
h2
1375.8270000108
1649.0919999778
1187
1478
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/sequence-theme.basic.css
h2
1376.1459999951
1404.991999967
3523
12206
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/img/menu_separator.png
h2
1735.9370000195
1890.9289999865
720
114
200
image/png
Image
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
h2
1736.6590000456
1847.9790000711
68676
131544
200
application/font-otf
Font
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
h2
1737.0939999819
1770.7860000664
66578
129908
200
application/font-otf
Font
https://www.sat.gob.mx/satys/font/icons3.woff2
h2
1749.0199999884
1854.8919999739
32123
41472
200
application/font-woff2
Font
https://www.sat.gob.mx/satys/font/icons3.ttf
h2
1775.9840000654
1879.6200000215
30344
46544
200
application/font-ttf
Font
https://www.google-analytics.com/analytics.js
h2
1841.1110000452
1846.4340000646
20630
50205
200
text/javascript
Script
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-bg_flat_75_ffffff_40x100.png
h2
1855.539000011
1888.7830000604
810
208
200
image/png
Image
https://webchat-cls30.i6.inconcertcc.com/v3/click_to_chat?token=E53C3AFFBBF0E3D91AA45D8605050A77
h2
1886.4150000736
2167.9129999829
9640
29628
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=143754210&t=pageview&_s=1&dl=https%3A%2F%2Fwww.sat.gob.mx%2Fhome&ul=en-us&de=UTF-8&dt=Portal%20de%20tr%C3%A1mites%20y%20servicios%20-%20SAT&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=324337637&gjid=1243377827&cid=507847429.1650246610&tid=UA-3112836-17&_gid=1742482499.1650246610&_r=1&_slc=1&z=708131179
h2
2165.1260000654
2177.6270000264
613
2
200
text/plain
XHR
https://chat1-cls30.i6.inconcertcc.com/inconcert/apps/webdesigner/lib/jquery/jquery-3.1.1.min.js
h2
2308.7359999772
2494.5549999829
30640
86751
200
application/x-javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1123.83
8.659
1133.246
10.512
1692.002
80.44
1772.456
10.864
1787.604
10.676
1806.858
36.542
1843.688
22.905
1869.413
60.576
1932.995
19.704
1962.61
25.792
1988.542
6.035
1996.238
175.53
2171.789
34.176
2216.544
96.77
2317.646
19.429
2343.155
5.789
2541.42
11.22
2557.254
5.366
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sat.gob.mx should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 105 KiB
Images can slow down the page's load time. Sat.gob.mx should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
114552
107967
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sat.gob.mx should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sat.gob.mx should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/satys/css/style.css?1.2
9854
2794
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sat.gob.mx should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/satys/js/datatables.responsive.js
8781
5158
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sat.gob.mx should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 125 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
64513
55747
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
25108
24624
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
28646
24420
https://www.sat.gob.mx/satys/js/datatables.js
27702
23083
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 420 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.sat.gob.mx/home
421.055
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sat.gob.mx should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
0
Avoids enormous network payloads — Total size was 1,221 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
144145
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
115311
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
100058
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
81634
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
68676
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
67076
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
66578
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
64513
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
41564
https://www.sat.gob.mx/satys/js/jquery.js
33953
Avoids an excessive DOM size — 624 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
624
Maximum DOM Depth
slider background
12
Maximum Child Elements
Personas  Asalariados  Arrendadores  Empresario…
16
Avoid chaining critical requests — 29 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sat.gob.mx should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.sat.gob.mx/home
444.623
24.229
5.434
https://www.sat.gob.mx/satys/js/jquery.js
71.476
54.678
1.785
Unattributable
68.689
3.375
0.156
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Rendering
289.038
Script Evaluation
174.695
Style & Layout
129.702
Other
95.267
Parse HTML & CSS
29.137
Script Parsing & Compilation
24.104
Keep request counts low and transfer sizes small — 52 requests • 1,221 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
52
1250748
Image
14
676669
Script
18
314055
Font
4
197721
Stylesheet
12
43042
Document
1
17537
Other
3
1724
Media
0
0
Third-party
4
61523
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
21243
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
slider background
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
slider background
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Trámites y servicios Para personas físicas
0.0024403467297084
v E D B U C A x Buzón Tributario
0.0023938595612444
Enlaces a otros organismos Instituto Nacional de Transparencia, Acceso a la In…
0.00071385097466759
Contacto Av. Hidalgo 77, Col. Guerrero, C.P. 06300, Ciudad de México. Atenció…
0.0005936525408827
Minisitio de Buzón Tributario
0.00044246913580247
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.sat.gob.mx/home
745
88
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
1
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sat.gob.mx on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.7 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Other

Efficiently encode images — Potential savings of 168 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
99280
59050
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
143359
57445
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
80862
19925
https://www.sat.gob.mx/satys/img/social_buttons.jpg
24547
19197
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
66303
16862
Serve images in next-gen formats — Potential savings of 402 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
143359
102337.3
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
99280
81676.1
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
80862
53935.75
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
66303
45140.35
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
114552
31197.55
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
40906
27261.7
https://www.sat.gob.mx/satys/img/social_buttons.jpg
24547
22047.9
https://www.sat.gob.mx/satys/img/logo3.png
18343
14802.85
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
30984
13533.75
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
25554
10371.75
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
21512
9388.05
Avoid multiple page redirects — Potential savings of 420 ms
Redirects can cause additional delays before the page can begin loading. Sat.gob.mx should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://sat.gob.mx/
190
https://wwwmat.sat.gob.mx/
230
https://www.sat.gob.mx/home
0

Other

Serve static assets with an efficient cache policy — 46 resources found
Sat.gob.mx can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
0
144145
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
0
115311
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
0
100058
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
0
81634
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
0
68676
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
0
67076
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
0
66578
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
0
64513
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
0
41564
https://www.sat.gob.mx/satys/js/jquery.js
0
33953
https://www.sat.gob.mx/satys/font/icons3.woff2
0
32123
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
0
31766
https://www.sat.gob.mx/satys/font/icons3.ttf
0
30344
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
0
28646
https://www.sat.gob.mx/satys/js/datatables.js
0
27702
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
0
26257
https://www.sat.gob.mx/satys/img/social_buttons.jpg
0
25155
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
0
25108
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
0
22211
https://www.sat.gob.mx/satys/img/logo3.png
0
18950
https://www.sat.gob.mx/satys/js/sequence.min.js
0
12833
https://www.sat.gob.mx/satys/js/moment.min.js
0
12542
https://www.sat.gob.mx/satys/js/owl.carousel.min.js
0
11150
https://www.sat.gob.mx/satys/css/style.css?1.2
0
9854
https://www.sat.gob.mx/satys/js/datatables.responsive.js
0
8781
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.css
0
7957
https://www.sat.gob.mx/satys/js/hammer.min.js
0
7077
https://www.sat.gob.mx/satys/js/main.js
0
6616
https://www.sat.gob.mx/satys/css/media_queries.css
0
6275
https://www.sat.gob.mx/satys/js/jsp.js
0
5443
https://www.sat.gob.mx/satys/js/swipe.js
0
4574
https://www.sat.gob.mx/satys/css/fullcalendar.min.css
0
3559
https://www.sat.gob.mx/satys/css/sequence-theme.basic.css
0
3523
https://www.sat.gob.mx/satys/css/datatables.css
0
3094
https://www.sat.gob.mx/satys/entrada/sliderengine/initslider-1.js
0
2464
https://www.sat.gob.mx/satys/css/sidebar.css?1.2
0
1881
https://www.sat.gob.mx/satys/css/slider.css
0
1876
https://www.sat.gob.mx/satys/css/owl.carousel.css
0
1762
https://www.sat.gob.mx/satys/js/es.js
0
1743
https://www.sat.gob.mx/satys/css/datatables.responsive.css
0
1288
https://www.sat.gob.mx/satys/css/jsp.css
0
1187
https://www.sat.gob.mx/satys/img/menu_search.png
0
1012
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-bg_flat_75_ffffff_40x100.png
0
810
https://www.sat.gob.mx/satys/css/all.css?1.1
0
786
https://www.sat.gob.mx/satys/img/menu_separator.png
0
720
https://www.google-analytics.com/analytics.js
7200000
20630
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
111.32000002544
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
33.692000084557
https://www.sat.gob.mx/satys/font/icons3.woff2
105.87199998554
https://www.sat.gob.mx/satys/font/icons3.ttf
103.63599995617
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
SHOW DETAILS
SHOW DETAILS
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.sat.gob.mx/satys/img/logo3.png
https://www.sat.gob.mx/satys/img/social_buttons.jpg
88

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of sat.gob.mx. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Sat.gob.mx may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

`[id]` attributes on active, focusable elements are not unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Failing Elements
Buzón Tributario

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.pw > div#icons > span > img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that sat.gob.mx should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.2
jQuery UI
1.11.4
Hammer.js
2.0.4
Moment.js
2.9.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.sat.gob.mx/satys/js/sequence.min.js
https://www.sat.gob.mx/satys/js/sequence.min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://sat.gob.mx/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 11 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
4
Medium
SHOW DETAILS
4
High
SHOW DETAILS
3
Medium
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for sat.gob.mx. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sat.gob.mx on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div.pw > div#icons > span > img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of sat.gob.mx. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sat.gob.mx on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 67
Performance 69
Accessibility 89
Best Practices 83
SEO 76
PWA 20
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.sat.gob.mx/home
Updated: 18th April, 2022

1.63 seconds
First Contentful Paint (FCP)
79%
12%
9%

0.01 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on mobile
69

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for sat.gob.mx. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 100 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sat.gob.mx should consider lazy-loading offscreen and hidden images.
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sat.gob.mx should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/satys/js/datatables.responsive.js
8782
5158
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sat.gob.mx should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 40 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.sat.gob.mx/home
37.033
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sat.gob.mx should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
0
Avoids enormous network payloads — Total size was 1,297 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
144145
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
115226
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
100058
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
81550
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
68679
https://www.sat.gob.mx/satys/font/SoberanaSans-Regular.otf
68537
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
66991
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
66576
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
64513
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
41564
Avoids an excessive DOM size — 624 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
624
Maximum DOM Depth
slider background
12
Maximum Child Elements
Personas  Asalariados  Arrendadores  Empresario…
16
Avoid chaining critical requests — 30 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sat.gob.mx should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.sat.gob.mx/home
729.744
77.476
18.932
https://www.sat.gob.mx/satys/js/jquery.js
276.86
206.356
6.748
Unattributable
264.052
11.2
0.672
https://www.google-analytics.com/analytics.js
100.948
90.448
3.312
https://www.sat.gob.mx/satys/js/sequence.min.js
98.556
28.584
3
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
98.152
69.616
14.84
https://chat1-cls30.i6.inconcertcc.com/inconcert/apps/webdesigner/lib/jquery/jquery-3.1.1.min.js
51.828
39.932
6.312
Minimizes main-thread work — 1.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
617.044
Style & Layout
440.244
Other
400.544
Rendering
156.36
Parse HTML & CSS
107.668
Script Parsing & Compilation
88.188
Keep request counts low and transfer sizes small — 55 requests • 1,297 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
55
1328008
Image
16
685362
Script
18
314025
Font
5
266257
Stylesheet
12
43151
Document
1
17530
Other
3
1683
Media
0
0
Third-party
4
61481
Minimize third-party usage — Third-party code blocked the main thread for 40 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
21244
37.208
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
slider background
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
LDeclaraciones ≡ KFactura electrónica ≡ MTrámites del RFC ≡ JAdeudos fiscales ≡…
0.091387934653309
Novedades - Presenta tu Declaración Anual 2021... - Régimen Simplificado de C…
0.0061013016658547
Buzón Tributario
0.0022641816495858
Devoluciones y compensaciones
0.00050409317016602
Otros trámites y servicios
0.00037635915419635
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.sat.gob.mx/satys/js/jquery.js
5490
149
https://www.sat.gob.mx/satys/js/jquery.js
2940
112
https://www.google-analytics.com/analytics.js
4132
96
https://chat1-cls30.i6.inconcertcc.com/inconcert/apps/webdesigner/lib/jquery/jquery-3.1.1.min.js
4967
50
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
1
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sat.gob.mx on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://sat.gob.mx/
http/1.1
0
150.03999997862
543
0
302
text/html
https://wwwmat.sat.gob.mx/
http/1.1
150.4319999367
462.36999996472
527
0
302
text/html
https://www.sat.gob.mx/home
h2
462.72599999793
498.76400001813
17530
88706
200
text/html
Document
https://www.sat.gob.mx/satys/css/all.css?1.1
h2
511.04699994903
586.2199999392
786
265
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/js/jquery.js
h2
511.35199994314
647.78699993622
33952
95933
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
h2
511.50599995162
534.56099994946
64513
240439
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/datatables.js
h2
511.93000003695
613.5559999384
27704
79615
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/datatables.responsive.js
h2
512.24599999841
535.25600000285
8782
25594
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/swipe.js
h2
512.36099994276
590.35900002345
4574
15252
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/jsp.js
h2
512.62900000438
593.46999996342
5445
14114
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/main.js
h2
512.88499997463
583.49699992687
6620
24833
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/owl.carousel.min.js
h2
513.0979999667
599.37900002114
11161
40402
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/hammer.min.js
h2
513.31099995878
546.70199996326
7076
18327
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/sequence.min.js
h2
513.54499999434
765.82700002473
12834
48192
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
h2
513.77499999944
759.87399998121
25105
137831
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/entrada/sliderengine/initslider-1.js
h2
514.01499996427
787.20599994995
2463
6757
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/moment.min.js
h2
514.33399994858
598.61099999398
12540
34743
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/css/fullcalendar.min.css
h2
514.52399999835
530.07400000934
3561
12100
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
h2
514.92699992377
617.51499993261
28644
94722
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/js/es.js
h2
515.12500003446
550.87299994193
1744
2234
200
application/x-javascript
Script
https://www.sat.gob.mx/satys/css/owl.carousel.css
h2
515.45800000895
599.10099999979
1763
4830
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/img/logo3.png
h2
788.87899999972
884.02999995742
18951
18343
200
image/png
Image
https://www.sat.gob.mx/satys/img/menu_search.png
h2
834.91800003685
927.43999999948
1014
406
200
image/png
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
h2
906.00299998187
938.50299995393
100058
99280
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
h2
906.10999998171
1147.0699999481
115226
114552
200
image/png
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
h2
906.24899999239
1008.3079999313
41564
40906
200
image/png
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
h2
906.39200003352
1146.4439999545
31766
30984
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
h2
906.54300001916
1112.0629999787
81550
80862
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
h2
906.80799994152
962.92700001504
66991
66303
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
h2
907.21500001382
1014.3469999311
22211
21512
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
h2
907.39399997983
942.61299993377
144145
143359
200
image/jpeg
Image
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
h2
907.48299995903
999.89099998493
26341
25554
200
image/jpeg
Image
https://www.sat.gob.mx/satys/img/social_buttons.jpg
h2
907.70999994129
1004.5389999868
25157
24547
200
image/jpeg
Image
https://www.sat.gob.mx/satys/css/style.css?1.2
h2
587.81499997713
608.367000008
9854
50940
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/sidebar.css?1.2
h2
588.14499992877
605.39899999276
1881
4893
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/media_queries.css
h2
588.29400001559
667.74900001474
6275
27172
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/datatables.css
h2
588.64400000311
605.77000002377
3095
17940
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/datatables.responsive.css
h2
588.92999996897
674.92599994875
1288
3157
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.css
h2
589.12299992517
672.8759999387
8035
30203
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/slider.css
h2
589.47699994314
662.75899996981
1903
6906
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/jsp.css
h2
589.79699993506
833.52300000843
1187
1478
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/css/sequence-theme.basic.css
h2
590.97999997903
649.68899998348
3523
12206
200
text/css
Stylesheet
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
h2
920.15999997966
1177.1629999857
66576
129908
200
application/font-otf
Font
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
h2
920.29499995988
1056.464000023
68679
131544
200
application/font-otf
Font
https://www.sat.gob.mx/satys/img/aa_bg.png
h2
930.5399999721
965.01599997282
1156
554
200
image/png
Image
https://www.sat.gob.mx/satys/font/icons3.ttf
h2
931.09299999196
1045.6380000105
30342
46544
200
application/font-ttf
Font
https://www.google-analytics.com/analytics.js
h2
988.37399994954
993.13800001983
20631
50205
200
text/javascript
Script
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-bg_flat_75_ffffff_40x100.png
h2
1001.8399999244
1093.5149999568
811
208
200
image/png
Image
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-bg_glass_75_ffffff_1x400.png
h2
1015.5729999533
1084.9790000357
812
207
200
image/png
Image
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-icons_888888_256x240.png
h2
1015.803999966
1101.3259999454
7609
6999
200
image/png
Image
https://www.sat.gob.mx/satys/font/icons3.woff2
h2
1027.36800001
1147.5319999736
32123
41472
200
application/font-woff2
Font
https://webchat-cls30.i6.inconcertcc.com/v3/click_to_chat?token=E53C3AFFBBF0E3D91AA45D8605050A77
h2
1037.003000034
1365.4819999356
9597
29628
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=988155269&t=pageview&_s=1&dl=https%3A%2F%2Fwww.sat.gob.mx%2Fhome&ul=en-us&de=UTF-8&dt=Portal%20de%20tr%C3%A1mites%20y%20servicios%20-%20SAT&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=621205050&gjid=1490361486&cid=2121147435.1650246629&tid=UA-3112836-17&_gid=106058529.1650246629&_r=1&_slc=1&z=1610389421
h2
1097.0599999418
1100.9250000352
613
2
200
text/plain
XHR
https://www.sat.gob.mx/satys/font/SoberanaSans-Regular.otf
h2
1184.1439999407
1333.210999961
68537
131096
200
application/font-otf
Font
https://chat1-cls30.i6.inconcertcc.com/inconcert/apps/webdesigner/lib/jquery/jquery-3.1.1.min.js
h2
1370.3599999426
1534.5779999625
30640
86751
200
application/x-javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
542.266
6.91
549.95
9.749
875.707
74.558
957.874
9.574
970.12
5.153
979.52
22.599
1003.767
21.514
1025.362
56.126
1096.101
17.106
1114.344
23.978
1142.162
13.723
1202.555
13.134
1221.372
17.417
1385.878
11.251
1581.601
12.558
1613.708
6.349
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 5.6 s
The time taken for the page to become fully interactive.
Speed Index — 3.9 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.101
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 150 ms
Users could experience a delay when interacting with the page.

Other

Properly size images — Potential savings of 97 KiB
Images can slow down the page's load time. Sat.gob.mx should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
114552
99184
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sat.gob.mx should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/satys/css/style.css?1.2
9854
2794

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 4.7 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 5.5 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 1,500 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sat.gob.mx should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.sat.gob.mx/satys/js/jquery.js
33952
150
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
64513
300
https://www.sat.gob.mx/satys/js/datatables.js
27704
150
https://www.sat.gob.mx/satys/js/swipe.js
4574
150
https://www.sat.gob.mx/satys/js/hammer.min.js
7076
150
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
25105
150
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
28644
150
Reduce unused JavaScript — Potential savings of 125 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
64513
55747
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
25105
24621
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
28644
24418
https://www.sat.gob.mx/satys/js/datatables.js
27704
23084
Efficiently encode images — Potential savings of 168 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
99280
59050
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
143359
57445
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
80862
19925
https://www.sat.gob.mx/satys/img/social_buttons.jpg
24547
19197
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
66303
16862
Serve images in next-gen formats — Potential savings of 402 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
143359
102337.3
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
99280
81676.1
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
80862
53935.75
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
66303
45140.35
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
114552
31197.55
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
40906
27261.7
https://www.sat.gob.mx/satys/img/social_buttons.jpg
24547
22047.9
https://www.sat.gob.mx/satys/img/logo3.png
18343
14802.85
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
30984
13533.75
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
25554
10371.75
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
21512
9388.05
Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Sat.gob.mx should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://sat.gob.mx/
630
https://wwwmat.sat.gob.mx/
780
https://www.sat.gob.mx/home
0
Serve static assets with an efficient cache policy — 49 resources found
Sat.gob.mx can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
0
144145
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
0
115226
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
0
100058
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
0
81550
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
0
68679
https://www.sat.gob.mx/satys/font/SoberanaSans-Regular.otf
0
68537
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
0
66991
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
0
66576
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.js
0
64513
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
0
41564
https://www.sat.gob.mx/satys/js/jquery.js
0
33952
https://www.sat.gob.mx/satys/font/icons3.woff2
0
32123
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
0
31766
https://www.sat.gob.mx/satys/font/icons3.ttf
0
30342
https://www.sat.gob.mx/satys/js/fullcalendar.min.js
0
28644
https://www.sat.gob.mx/satys/js/datatables.js
0
27704
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
0
26341
https://www.sat.gob.mx/satys/img/social_buttons.jpg
0
25157
https://www.sat.gob.mx/satys/entrada/sliderengine/amazingslider.js
0
25105
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
0
22211
https://www.sat.gob.mx/satys/img/logo3.png
0
18951
https://www.sat.gob.mx/satys/js/sequence.min.js
0
12834
https://www.sat.gob.mx/satys/js/moment.min.js
0
12540
https://www.sat.gob.mx/satys/js/owl.carousel.min.js
0
11161
https://www.sat.gob.mx/satys/css/style.css?1.2
0
9854
https://www.sat.gob.mx/satys/js/datatables.responsive.js
0
8782
https://www.sat.gob.mx/satys/js/jquery-ui/jquery-ui.min.css
0
8035
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-icons_888888_256x240.png
0
7609
https://www.sat.gob.mx/satys/js/hammer.min.js
0
7076
https://www.sat.gob.mx/satys/js/main.js
0
6620
https://www.sat.gob.mx/satys/css/media_queries.css
0
6275
https://www.sat.gob.mx/satys/js/jsp.js
0
5445
https://www.sat.gob.mx/satys/js/swipe.js
0
4574
https://www.sat.gob.mx/satys/css/fullcalendar.min.css
0
3561
https://www.sat.gob.mx/satys/css/sequence-theme.basic.css
0
3523
https://www.sat.gob.mx/satys/css/datatables.css
0
3095
https://www.sat.gob.mx/satys/entrada/sliderengine/initslider-1.js
0
2463
https://www.sat.gob.mx/satys/css/slider.css
0
1903
https://www.sat.gob.mx/satys/css/sidebar.css?1.2
0
1881
https://www.sat.gob.mx/satys/css/owl.carousel.css
0
1763
https://www.sat.gob.mx/satys/js/es.js
0
1744
https://www.sat.gob.mx/satys/css/datatables.responsive.css
0
1288
https://www.sat.gob.mx/satys/css/jsp.css
0
1187
https://www.sat.gob.mx/satys/img/aa_bg.png
0
1156
https://www.sat.gob.mx/satys/img/menu_search.png
0
1014
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-bg_glass_75_ffffff_1x400.png
0
812
https://www.sat.gob.mx/satys/js/jquery-ui/images/ui-bg_flat_75_ffffff_40x100.png
0
811
https://www.sat.gob.mx/satys/css/all.css?1.1
0
786
https://www.google-analytics.com/analytics.js
7200000
20631
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.sat.gob.mx/satys/font/SoberanaSans-Light.otf
257.00300000608
https://www.sat.gob.mx/satys/font/SoberanaSans-Bold.otf
136.16900006309
https://www.sat.gob.mx/satys/font/icons3.ttf
114.54500001855
https://www.sat.gob.mx/satys/font/icons3.woff2
120.16399996355
https://www.sat.gob.mx/satys/font/SoberanaSans-Regular.otf
149.0670000203
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
SHOW DETAILS
SHOW DETAILS
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175044609&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175189778&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461175112417&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786106&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173786120&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461174376747&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232193&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173217305&ssbinary=true
https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173232181&ssbinary=true
https://www.sat.gob.mx/satys/img/logo3.png
https://www.sat.gob.mx/satys/img/social_buttons.jpg
First Contentful Paint (3G) — 8039 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
89

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of sat.gob.mx. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Sat.gob.mx may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

ARIA input fields do not have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
Failing Elements
Personas

Navigation

`[id]` attributes on active, focusable elements are not unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Failing Elements
Buzón Tributario

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div#mob_head > div#mob_icons > span > img

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that sat.gob.mx should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.2
jQuery UI
1.11.4
Hammer.js
2.0.4
Moment.js
2.9.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.sat.gob.mx/satys/js/sequence.min.js
https://www.sat.gob.mx/satys/js/sequence.min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://sat.gob.mx/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 11 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
4
Medium
SHOW DETAILS
4
High
SHOW DETAILS
3
Medium
76

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for sat.gob.mx. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sat.gob.mx on mobile screens.
Document uses legible font sizes — 99.8% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
SHOW DETAILS
.seq .seq-pagination > *
0.20%
0px
SHOW DETAILS
.seq .seq-canvas
0.00%
0px
SHOW DETAILS
SHOW DETAILS
0.00%
0px
SHOW DETAILS
99.80%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Mobile Friendly

Tap targets are not sized appropriately — 97% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
x
23x22
A

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div#mob_head > div#mob_icons > span > img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
20

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of sat.gob.mx. This includes details about web app manifests.

PWA Optimized

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sat.gob.mx on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 200.33.84.233
Continent: North America
Country: Mexico
Mexico Flag
Region:
City:
Longitude: -99.0111
Latitude: 19.4371
Currencies: MXN
Languages: Spanish

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 90/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.sat.gob.mx
Issued By: GlobalSign RSA OV SSL CA 2018
Valid From: 3rd June, 2021
Valid To: 5th July, 2022
Subject: CN = www.sat.gob.mx
O = Servicio de Administración Tributaria
L = Ciudad de México
S = MX
Hash: 4ab7fe86
Issuer: CN = GlobalSign RSA OV SSL CA 2018
O = GlobalSign nv-sa
S = BE
Version: 2
Serial Number: 12474812101149568035705006797
Serial Number (Hex): 284EEC37121C16AC2DE72ACD
Valid From: 3rd June, 2024
Valid To: 5th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:F8:EF:7F:F2:CD:78:67:A8:DE:6F:8F:24:8D:88:F1:87:03:02:B3:EB
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.4146.1.20
CPS: https://www.globalsign.com/repository/
Policy: 2.23.140.1.2.2
Authority Information Access: CA Issuers - URI:http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
OCSP - URI:http://ocsp.globalsign.com/gsrsaovsslca2018
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Jun 3 22:11:04.648 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:ED:EF:CA:67:71:1C:43:64:C5:3F:52:
BF:77:D8:B8:D1:FC:44:D7:D7:07:5A:BD:43:10:84:A8:
F1:E1:90:16:EF:02:20:12:9F:D3:58:58:69:31:0D:06:
B2:9C:7F:0B:62:BA:5B:97:AD:59:CC:B4:53:86:74:A4:
C2:A1:0B:9D:8B:CE:B3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jun 3 22:11:04.649 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8E:8B:91:C7:EA:0A:81:C4:FF:66:9C:
CE:00:64:71:76:C2:3F:25:7D:01:8B:4F:8E:5C:53:75:
82:77:53:13:5A:02:20:07:56:05:FA:32:81:64:BB:79:
AA:F9:16:11:49:D6:D4:D2:12:11:34:E4:F8:BA:EF:63:
A8:19:59:C3:F9:FE:CA
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
Timestamp : Jun 3 22:11:04.689 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:12:BE:E2:7A:E2:5A:96:28:D7:07:BC:F2:
B9:96:68:85:AB:A6:A9:80:0E:3B:3D:6F:0A:11:CC:1F:
B1:D2:8B:B9:02:20:34:27:FD:D1:01:CF:0F:06:FD:5E:
21:56:69:75:B3:77:AA:43:44:C3:57:D7:33:2C:66:8E:
5A:BC:44:82:C5:BB
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sat.gob.mx
DNS:www.sat.gob.mx
Technical

DNS Lookup

A Records

Host IP Address Class TTL
sat.gob.mx. 200.33.84.233 IN 300

NS Records

Host Nameserver Class TTL
sat.gob.mx. ns1-05.azure-dns.com. IN 300
sat.gob.mx. ns2-05.azure-dns.net. IN 300
sat.gob.mx. ns3-05.azure-dns.org. IN 300
sat.gob.mx. ns4-05.azure-dns.info. IN 300

MX Records

Priority Host Server Class TTL
5 sat.gob.mx. mx.sat.gob.mx. IN 300
0 sat.gob.mx. mx1.sat.gob.mx. IN 300

SOA Records

Domain Name Primary NS Responsible Email TTL
sat.gob.mx. ns1-05.azure-dns.com. seguridad.sat.gob.mx. 300

TXT Records

Host Value Class TTL
sat.gob.mx. v=spf1 IN 1800
sat.gob.mx. MS=37B3EA4A77F1E456D15CD4599E82923FDA315A2A IN 1800
sat.gob.mx. +e8DlX18RkA86DHxA8KR8Pc0ZH0VNGARCb+uqK071XWek8Y0olDFZgJAOeNXEMnrbg7pXeVkr/B1ZX+EjwplyQ== IN 1800
sat.gob.mx. google-site-verification=XdfR63wng0VZx0vjN4YncgBYQyVxUh_DGvRhuTKByTg IN 1800
sat.gob.mx. google-site-verification=8xk82puynWbLomAMRHSOiu4yT-NzjeaQy-Q5_vDEH0g IN 1800
sat.gob.mx. _globalsign-domain-verification=daQFuqoh6nPSa_NA-DrJ1B_S3YJ9yOg30cC87p6bwd IN 1800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Date: 17th April, 2022
Server: Oracle-HTTP-Server Oracle-Web-Cache-11g/11.1.1.9.0 (H;max-age=214747847+0;age=62298;ecid=2040854418949713,0:1)
Cache-Control: no-cache
Connection: keep-alive
Last-Modified: 17th April, 2022
host_service: FutureTenseContentServer:11.1.1.8.0
Content-Language: en
Via: 1.1 wwwmat.sat.gob.mx (Access Gateway-ag-AEBE4AC6BC92D6DB-52521359), 1.1 b759e26bde22770788987f2078515d9a.cloudfront.net (CloudFront)
Vary: Accept-Encoding
X-Cache: Hit from cloudfront
X-Amz-Cf-Pop: EWR53-C2
X-Amz-Cf-Id: UDTYyU9wx8iFXz_feBg1nvm0EnnIgi3KZqkBI0-fujcHAH6jhIc-AQ==
Age: 6261

Whois Lookup

Created: 18th February, 1998
Changed: 18th February, 2022
Expires: 17th February, 2023
Registrar: AKKY ONLINE SOLUTIONS, S.A. DE C.V.
Status:
Nameservers: huitzilopochtli.sat.gob.mx
ns1-05.azure-dns.com
ns2.sat.gob.mx
tlahuizcalpantecuhtli.sat.gob.mx
Owner Name: Servicio de Administracion Tributaria
Owner City: Distrito Federal
Owner State: Distrito Federal
Owner Country: Mexico
Admin Name: Administrador Seguridad de la informacion
Admin City: Mexico D.F.
Admin State: Distrito Federal
Admin Country: Mexico
Tech Name: Administrador Seguridad de la Informacion
Tech City: Mexico D.F.
Tech State: Distrito Federal
Tech Country: Mexico
Billing Name: Administrador Seguridad de la informacion
Billing City: Mexico D.F.
Billing State: Distrito Federal
Billing Country: Mexico
Full Whois:
Domain Name: sat.gob.mx

Created On: 1998-02-18
Expiration Date: 2023-02-17
Last Updated On: 2022-02-18
Registrar: AKKY ONLINE SOLUTIONS, S.A. DE C.V.
URL: http://www.akky.mx
Whois TCP URI: whois.akky.mx
Whois Web URL: http://www.akky.mx/herramientas/whois.jsf

Registrant:
Name: Servicio de Administracion Tributaria
City: Distrito Federal
State: Distrito Federal
Country: Mexico

Administrative Contact:
Name: Administrador Seguridad de la informacion
City: Mexico D.F.
State: Distrito Federal
Country: Mexico

Technical Contact:
Name: Administrador Seguridad de la Informacion
City: Mexico D.F.
State: Distrito Federal
Country: Mexico

Billing Contact:
Name: Administrador Seguridad de la informacion
City: Mexico D.F.
State: Distrito Federal
Country: Mexico

Name Servers:
DNS: huitzilopochtli.sat.gob.mx 200.57.3.8
DNS: tlahuizcalpantecuhtli.sat.gob.mx 200.33.74.41
DNS: ns1-05.azure-dns.com
DNS: ns2.sat.gob.mx 52.55.198.38

DNSSEC DS Records:


% NOTICE: The expiration date displayed in this record is the date the
% registrar's sponsorship of the domain name registration in the registry is
% currently set to expire. This date does not necessarily reflect the
% expiration date of the domain name registrant's agreement with the sponsoring
% registrar. Users may consult the sponsoring registrar's Whois database to
% view the registrar's reported date of expiration for this registration.

% The requested information ("Information") is provided only for the delegation
% of domain names and the operation of the DNS administered by NIC Mexico.

% It is absolutely prohibited to use the Information for other purposes,
% including sending not requested emails for advertising or promoting products
% and services purposes (SPAM) without the authorization of the owners of the
% Information and NIC Mexico.

% The database generated from the delegation system is protected by the
% intellectual property laws and all international treaties on the matter.

% If you need more information on the records displayed here, please contact us
% by email at ayuda@nic.mx .

% If you want notify the receipt of SPAM or unauthorized access, please send a
% email to abuse@nic.mx .

% NOTA: La fecha de expiracion mostrada en esta consulta es la fecha que el
% registrar tiene contratada para el nombre de dominio en el registry. Esta
% fecha no necesariamente refleja la fecha de expiracion del nombre de dominio
% que el registrante tiene contratada con el registrar. Puede consultar la base
% de datos de Whois del registrar para ver la fecha de expiracion reportada por
% el registrar para este nombre de dominio.

% La informacion que ha solicitado se provee exclusivamente para fines
% relacionados con la delegacion de nombres de dominio y la operacion del DNS
% administrado por NIC Mexico.

% Queda absolutamente prohibido su uso para otros propositos, incluyendo el
% envio de Correos Electronicos no solicitados con fines publicitarios o de
% promocion de productos y servicios (SPAM) sin mediar la autorizacion de los
% afectados y de NIC Mexico.

% La base de datos generada a partir del sistema de delegacion, esta protegida
% por las leyes de Propiedad Intelectual y todos los tratados internacionales
% sobre la materia.

% Si necesita mayor informacion sobre los registros aqui mostrados, favor de
% comunicarse a ayuda@nic.mx.

% Si desea notificar sobre correo no solicitado o accesos no autorizados, favor
% de enviar su mensaje a abuse@nic.mx.

View Raw Whois

Nameservers

Name IP Address
huitzilopochtli.sat.gob.mx 200.57.3.8
ns1-05.azure-dns.com 13.107.236.5
ns2.sat.gob.mx 52.55.198.38
tlahuizcalpantecuhtli.sat.gob.mx 200.33.74.41
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
inegi.gob.mx
$2,785 USD 1/5
infonavit.gob.mx
$905 USD 1/5
pemex.com
$51,928 USD 2/5
presidencia.gob.mx
$4,531 USD 2/5
profeco.gob.mx
$11,869 USD 3/5
All sites similar to sat.gob.mx

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
sat.com
0/5
sat.com.br
0/5
sat.com.mx
0/5
sat.com.py
0/5
sat.de
$20 USD

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

sat.gob.mx Infographic

sat.gob.mx by the numbers infographic

Recently Updated

cartoons8.tv
youtube.com
actitle.com
swomagazine.com
funhub.pk
zamunda.net
netfucks.com
websitesball.com
secretbristol.com
roblox.com

Recently Viewed

acsedu.com
grainemporium.com
gloshippers.com
asahi-mullion.com
wundercounter.com
berusk.com
cashfat.com
drbackup.net
agzyd.com
apotheke4all.net