7.1 sec in total
1.8 sec
5 sec
324 ms
Click here to check amazing OMA content for Mexico. Otherwise, check out these important facts you probably never knew about oma.aero
oma
Visit oma.aeroWe analyzed Oma.aero page load time and found that the first response time was 1.8 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oma.aero performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value11.9 s
0/100
25%
Value8.7 s
16/100
10%
Value3,120 ms
2/100
30%
Value0.017
100/100
15%
Value14.9 s
8/100
10%
1781 ms
133 ms
416 ms
1014 ms
184 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 92% of them (61 requests) were addressed to the original Oma.aero, 3% (2 requests) were made to Apps.shareholder.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Oma.aero.
Page size can be reduced by 412.4 kB (31%)
1.3 MB
925.5 kB
In fact, the total size of Oma.aero main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 35.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 18.0 kB, which is 44% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.3 kB or 86% of the original size.
Potential reduce by 172.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, OMA needs image optimization as it can save up to 172.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 136.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 136.2 kB or 65% of the original size.
Potential reduce by 68.4 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Oma.aero needs all CSS files to be minified and compressed as it can save up to 68.4 kB or 83% of the original size.
Number of requests can be reduced by 46 (72%)
64
18
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OMA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
oma.aero
1781 ms
133 ms
common.css
416 ms
common.js
1014 ms
slideshow.js
184 ms
init.js
127 ms
jquery.ctrotator.css
125 ms
jquery-1.2.6.pack.js
689 ms
jquery.ctrotator.js
247 ms
jquery.ctrotator.bridge.li.js
188 ms
irxml.aspx
86 ms
irxml.functions.js
42 ms
5-22-09_OMAB_stockquo.gif
61 ms
background_main.gif
64 ms
background_header_main.gif
88 ms
logo_main.gif
126 ms
h_busqueda.gif
88 ms
button_ir.gif
89 ms
bg-sprite-y.png
127 ms
button_language.gif
124 ms
nav_somos.gif
127 ms
background_nav_option.png
128 ms
nav_aeropuertos.gif
129 ms
nav_plaza.gif
188 ms
nav_carga.gif
189 ms
nav_relacion.gif
193 ms
nav_prensa.gif
193 ms
nav_empleo.gif
190 ms
logo_oma_plaza.png
250 ms
7033.jpg
795 ms
7182.jpg
2055 ms
7143.png
827 ms
5379.png
254 ms
5359.png
257 ms
5356.png
312 ms
5388.png
314 ms
5391.png
315 ms
5513.png
375 ms
5364.png
376 ms
5384.png
377 ms
5368.png
436 ms
5512.gif
436 ms
7146.png
560 ms
5352_alternate.jpg
856 ms
5714_alternate.jpg
614 ms
background_right_h.gif
615 ms
background_bottom_right_h.gif
676 ms
subnav_main.gif
677 ms
acapulco.gif
738 ms
ga.js
40 ms
reynosa.gif
691 ms
__utm.gif
12 ms
ciudad-juarez.gif
728 ms
san-luis-potosi.gif
727 ms
culiacan.gif
771 ms
tampico.gif
751 ms
chihuahua.gif
752 ms
torreon.gif
765 ms
durango.gif
794 ms
zacatecas.gif
802 ms
mazatlan.gif
809 ms
zihuatanejo.gif
751 ms
monterrey.gif
764 ms
row.gif
790 ms
background_stocks.gif
797 ms
print.css
63 ms
oma.aero accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
oma.aero best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
oma.aero SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oma.aero can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Oma.aero main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
oma.aero
Open Graph description is not detected on the main page of OMA. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: