4.4 sec in total
34 ms
3.4 sec
968 ms
Click here to check amazing Maiair content for Myanmar. Otherwise, check out these important facts you probably never knew about maiair.com
myanmar airway international, aung augn zaw, Aung Aung Zaw, mai airline, mai, mai myanmar, maiair, myanmar airways, mai air, mai airlines, myanmar airway international, www.maiair.com, mai flight, mai...
Visit maiair.comWe analyzed Maiair.com page load time and found that the first response time was 34 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
maiair.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value35.6 s
0/100
25%
Value9.6 s
11/100
10%
Value590 ms
50/100
30%
Value1.336
0/100
15%
Value14.3 s
9/100
10%
34 ms
945 ms
269 ms
70 ms
39 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 85% of them (96 requests) were addressed to the original Maiair.com, 5% (6 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Book-myanmar.crane.aero. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Maiair.com.
Page size can be reduced by 538.9 kB (6%)
9.3 MB
8.8 MB
In fact, the total size of Maiair.com main page is 9.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. Only a small number of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.
Potential reduce by 286.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 286.2 kB or 60% of the original size.
Potential reduce by 238.1 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. Maiair images are well optimized though.
Potential reduce by 6.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.7 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. Maiair.com has all CSS files already compressed.
Number of requests can be reduced by 43 (42%)
103
60
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maiair. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
maiair.com
34 ms
maiair.com
945 ms
bootstrap.min.css
269 ms
select2.min.css
70 ms
select2-bootstrap.min.css
39 ms
daterangepicker.css
42 ms
sweetalert2.min.css
40 ms
avu3dan.css
36 ms
tether.min.css
53 ms
bootstrap-grid.min.css
57 ms
bootstrap-reboot.min.css
56 ms
styles.css
77 ms
dropdown.css
74 ms
intlTelInput.min.css
74 ms
template.css
90 ms
alertify.min.css
96 ms
default.css
98 ms
jquery.min.js
97 ms
jquery-ui.min.js
119 ms
popper.min.js
101 ms
select2.full.min.js
113 ms
moment.min.js
121 ms
alertify.min.js
118 ms
template.js
130 ms
esabcmn.js
206 ms
esabcmn.js
476 ms
esabcmn.js
799 ms
esabcmn.js
399 ms
js
69 ms
swiper-bundle.min.css
135 ms
swiper-bundle.min.js
137 ms
p.css
35 ms
css2
31 ms
email-decode.min.js
4 ms
mobile.css
21 ms
alertify.min.css
18 ms
tether.min.js
17 ms
bootstrap.min.js
15 ms
sweetalert2.min.js
31 ms
smooth-scroll.js
36 ms
script.min.js
31 ms
jquery.touch-swipe.min.js
93 ms
script.js
94 ms
cookie.js
95 ms
intlTelInput.min.js
94 ms
vef91dfe02fce4ee0ad053f6de4f175db1715022073587
96 ms
gtm.js
139 ms
info_ico.svg
78 ms
1_baggage.png
206 ms
mingalar.png
185 ms
1_seat.png
315 ms
1_meal.png
316 ms
1_vip.png
1272 ms
1_wheelchair.png
480 ms
punhlaing.png
475 ms
loading-bubbles.svg
475 ms
logo_mai.png
75 ms
search.svg
77 ms
ic_language.svg
74 ms
20240517_-_Doha_Website_Banner_Design.jpg
79 ms
20240520_-_Slide_2_-_BKK_KUL__SIN.jpg
176 ms
20240520_-_Slide_3_-_HAN_ICN_DXB__DEL.jpg
177 ms
20240520_-_Slide_4_-_SGN_CAN_PNH__CNX.jpg
179 ms
20240520_-_Slide_5_-_OVB_CCU_HKT__MAA.jpg
178 ms
20240520_-_Slide_6_-_MDL_MYT_KET__PBU.jpg
180 ms
20240520_-_Slide_7_-_MGZ_TVY_KAW__AKY.jpg
177 ms
Switcharrow.svg
198 ms
ic_change.svg
201 ms
ic_baggage.svg
200 ms
ic_seat.svg
198 ms
ic_meal.svg
195 ms
ic_vip.svg
201 ms
ic_wheelchair.svg
310 ms
ic_hospital.svg
308 ms
e-Visa_Logo_99x_116.png
312 ms
MAI_visa.png
308 ms
SE.png
307 ms
img_incheon.png
311 ms
img_kualalumpur.png
475 ms
img_bangkok.png
475 ms
Delhi_236_x_183.jpg
471 ms
MAI_logo.jpg
470 ms
Announcements.png
473 ms
A320.jpg
470 ms
logo_mai.png
558 ms
ic_facebook.svg
555 ms
ic_twitter.svg
557 ms
ic_instagram.svg
553 ms
ic_linkedin.svg
555 ms
appstore.png
555 ms
googleplay.png
562 ms
master.svg
493 ms
visa.svg
498 ms
mpu.svg
496 ms
jcb.svg
490 ms
unionpay.svg
444 ms
ic_deaprt.svg
409 ms
ic_passenger.svg
406 ms
ic_flight_blue.svg
407 ms
ic_managebooking.svg
409 ms
ic_onlinecheckin.svg
407 ms
ic_flightstatus.svg
439 ms
KFOmCnqEu92Fr1Me5Q.ttf
293 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
371 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
374 ms
KFOkCnqEu92Fr1MmgWxP.ttf
377 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
376 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
374 ms
icomoon.ttf
1056 ms
subscribe_bg.png
379 ms
index.php
370 ms
icomoon.woff
780 ms
20240524_-_Vietiane_Design.jpg
50 ms
maiair.com accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
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
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
maiair.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
maiair.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Document doesn't have a valid hreflang
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maiair.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Maiair.com 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.
maiair.com
Open Graph description is not detected on the main page of Maiair. 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: