1.8 sec in total
90 ms
1.1 sec
565 ms
Visit imax.com now to see the best up-to-date IMAX content for United States and also check out these interesting facts you probably never knew about imax.com
| IMAX
Visit imax.comWe analyzed Imax.com page load time and found that the first response time was 90 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
imax.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value30.7 s
0/100
25%
Value19.3 s
0/100
10%
Value3,730 ms
1/100
30%
Value0.651
9/100
15%
Value38.8 s
0/100
10%
90 ms
167 ms
33 ms
71 ms
58 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 71% of them (40 requests) were addressed to the original Imax.com, 5% (3 requests) were made to Netdna.bootstrapcdn.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (659 ms) belongs to the original domain Imax.com.
Page size can be reduced by 2.1 MB (28%)
7.5 MB
5.4 MB
In fact, the total size of Imax.com main page is 7.5 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. 70% of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 47.6 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 6.3 kB, which is 11% 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 47.6 kB or 84% of the original size.
Potential reduce by 444.0 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. IMAX images are well optimized though.
Potential reduce by 349.1 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 349.1 kB or 68% of the original size.
Potential reduce by 1.2 MB
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. Imax.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 88% of the original size.
Number of requests can be reduced by 19 (38%)
50
31
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMAX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
imax.com
90 ms
www.imax.com
167 ms
css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css
33 ms
css_cw4bnvRT32hUwV7sG1paGMXRZeTG6Wlq2d4j9aqT4vA.css
71 ms
css_wJuXzEcE8BR12Bl544nsxFKHWslMsMkw-GSlbA_ZIOw.css
58 ms
bootstrap.min.css
8 ms
css_kQNE_c71zEXW-eRq1PZfqDTv7mI3RH6rFyh9Ml8_o0Q.css
113 ms
js_MpKfe1sTh5JIVGCZ17DsAuT1rqAC38MLLlkjqjQ1X_k.js
92 ms
js_ek4wm4e0MHsCeOa_O5BfdRUGzzavK3StCJkUBIhNv-E.js
73 ms
bootstrap.min.js
15 ms
js_qJql29HfRMZWW1ygesW1tQ8YYlWucGRvOEB38HtvNog.js
93 ms
js_-ZM1Un6a6V56l9CtHvCqd6ol8L6AdfROpLH5Xok5MA0.js
162 ms
js_iiro2olv-RX3gC3Gs2RbWAN3fitln8gMi7wDaiQWkFg.js
107 ms
js_a9OosoRSMtpWeOEZ3j9UWC8OPx46FMMqohEr69QV3RI.js
198 ms
js_B2uv6dkjoYobfQVyuXdchgrpnnx4oM0TkP_bDVf8Qrg.js
156 ms
player_api
230 ms
froogaloop2.min.js
190 ms
logo_sprite.png
162 ms
menu-search-icons_desktop.png
161 ms
flags.png
162 ms
deadpool_02.jpg
248 ms
GOE_IMAXArt_HomePagePromo_926x1460.jpg
356 ms
Zootopia5579e34cd2f2d.jpg
201 ms
10CFLN_IMAX_MainPagePromo_926x1460.jpg
249 ms
Allegiant_HomePagePromo_926x1460.jpg
407 ms
DF-12899_1500x924.jpg
249 ms
DF-12899_1500x924.jpg
626 ms
btn-play.png
278 ms
logo-home.png
278 ms
ALLEGIANT_900x600.jpg
392 ms
Allegiant_P1_1500x924.jpg
659 ms
GOE_1500x580.jpg
428 ms
ABP_MovieSliderImage_1500x580.jpg
452 ms
DF-17373R_1500x580.jpg
451 ms
introl.png
453 ms
proxima_nova_reg.woff
450 ms
proxima_nova_sbold.woff
451 ms
proxima_nova_light.woff
520 ms
proxima_nova_thin.woff
520 ms
proxima_nova_bold.woff
520 ms
proxima_nova_xbold.woff
518 ms
proxima_nova_black.woff
567 ms
analytics.js
149 ms
fontawesome-webfont.woff
490 ms
glyphicons-halflings-regular.woff
435 ms
glyphicons-halflings-regular.woff
24 ms
collect
18 ms
www-widgetapi.js
62 ms
collect
82 ms
YLehoqYfunw
46 ms
www-embed-player-vflZsBgOl.css
48 ms
www-embed-player.js
79 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
99 ms
ad_status.js
98 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
98 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
97 ms
imax.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
imax.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
imax.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
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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imax.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Imax.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.
imax.com
Open Graph description is not detected on the main page of IMAX. 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: