1.1 sec in total
35 ms
928 ms
177 ms
Click here to check amazing Mobile Cinemark content for United States. Otherwise, check out these important facts you probably never knew about mobile.cinemark.com
Visit mobile.cinemark.comWe analyzed Mobile.cinemark.com page load time and found that the first response time was 35 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
mobile.cinemark.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value6.1 s
12/100
25%
Value8.8 s
15/100
10%
Value1,750 ms
10/100
30%
Value0
100/100
15%
Value15.6 s
6/100
10%
35 ms
579 ms
45 ms
41 ms
39 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 51% of them (23 requests) were addressed to the original Mobile.cinemark.com, 47% (21 requests) were made to Cinemark.com and 2% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (579 ms) belongs to the original domain Mobile.cinemark.com.
Page size can be reduced by 172.4 kB (17%)
986.9 kB
814.5 kB
In fact, the total size of Mobile.cinemark.com main page is 986.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 736.9 kB which makes up the majority of the site volume.
Potential reduce by 152.8 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 33.0 kB, which is 19% 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 152.8 kB or 87% of the original size.
Potential reduce by 0 B
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. Mobile Cinemark images are well optimized though.
Potential reduce by 8.6 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 8.6 kB or 20% of the original size.
Potential reduce by 10.9 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. Mobile.cinemark.com needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 35% of the original size.
Number of requests can be reduced by 8 (21%)
39
31
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Cinemark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
mobile.cinemark.com
35 ms
mobile.cinemark.com
579 ms
core
45 ms
slick
41 ms
jquery-ui-1.13.1.min.css
39 ms
theater.css
19 ms
theaterSearch.css
61 ms
showtimes.css
41 ms
icons.svg
129 ms
icon_close_red.png
126 ms
btlbtl-earlyscreenings_200x300.png
154 ms
videoOverlay.png
103 ms
icon_location_large.png
103 ms
icon_search_large.png
103 ms
md_bjbj_poster_updated.gif
149 ms
med-dp3-1sht-poster.jpg
143 ms
reagan_poster_medium.jpg
151 ms
med-ar-xd-poster.png
143 ms
med-afraid-poster.jpg
159 ms
med-coraline-15th-poster.png
163 ms
med-twister-new-poster.jpg
169 ms
med-cityofdreams-poster.png
170 ms
1992_poster_medium.jpg
167 ms
med-thefrontroom-poster.png
173 ms
med-am-i-poster.jpg
180 ms
med-sne-poster.jpg
187 ms
med-transformers-one-poster.png
188 ms
med-iewu-poster.jpg
185 ms
med-the-forge-nposter.jpg
186 ms
med-slingshot-poster.png
194 ms
med-ygb-poster.jpg
198 ms
400-alien-romulus-banner1.jpg
205 ms
400-1992-tyrese-movie-banner.jpg
236 ms
400-august-movies-banner.jpg
235 ms
rocket-loader.min.js
68 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
140 ms
cinemarkLogo.png
94 ms
google-play-badge_updated.png
163 ms
apple-app-store-badge_updated.png
146 ms
WorkSans-Regular.woff
59 ms
WorkSans-SemiBold.woff
51 ms
WorkSans-Bold.woff
58 ms
main.js
22 ms
cnk-arrows.woff
26 ms
jquery-3.6.0.min.js
42 ms
mobile.cinemark.com accessibility score
mobile.cinemark.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mobile.cinemark.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.cinemark.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 Mobile.cinemark.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.
mobile.cinemark.com
Open Graph description is not detected on the main page of Mobile Cinemark. 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: