3.2 sec in total
230 ms
2.7 sec
286 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 230 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
oma.aero performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value9.2 s
1/100
25%
Value7.7 s
25/100
10%
Value200 ms
89/100
30%
Value0.023
100/100
15%
Value11.2 s
20/100
10%
230 ms
152 ms
14 ms
264 ms
468 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 88% of them (37 requests) were addressed to the original Oma.aero, 5% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (761 ms) belongs to the original domain Oma.aero.
Page size can be reduced by 895.6 kB (35%)
2.6 MB
1.7 MB
In fact, the total size of Oma.aero main page is 2.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 115.5 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 26.2 kB, which is 20% 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 115.5 kB or 89% of the original size.
Potential reduce by 150.3 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. OMA images are well optimized though.
Potential reduce by 513.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 513.2 kB or 80% of the original size.
Potential reduce by 116.6 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 116.6 kB or 85% of the original size.
Number of requests can be reduced by 19 (50%)
38
19
The browser has sent 38 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 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
oma.aero
230 ms
152 ms
fbevents.js
14 ms
moment.js
264 ms
moment-timezone-with-data.js
468 ms
swiper.min.css
271 ms
pikaday.css
209 ms
style.css
409 ms
jquery.min.js
381 ms
instantsearch.min.js
44 ms
paging.js
281 ms
multilevelpush.js
274 ms
fullexpandcollapse.js
275 ms
swiper.min.js
417 ms
pikaday.js
417 ms
common.js
351 ms
jquery.modal.min.js
387 ms
css
31 ms
search-light.png
252 ms
6147.png
761 ms
6201.png
506 ms
left-slider-arrow.png
247 ms
right-slider-arrow.png
248 ms
6045.png
257 ms
oma-premium-lounge-logo.png
316 ms
6046.png
451 ms
buzon-de-sugerencias.png
314 ms
6121.jpg
390 ms
home-general-info.jpeg
516 ms
estela-large.png
387 ms
news-large.png
456 ms
telephone-large.png
460 ms
briefcase-large.png
521 ms
6056.png
656 ms
6081.jpg
596 ms
facebook.png
571 ms
twitter.png
584 ms
linkedin.png
589 ms
instagram.png
640 ms
home.png
652 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf
212 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
219 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
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
oma.aero SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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: