8.6 sec in total
201 ms
8.1 sec
306 ms
Welcome to mirage.com homepage info - get ready to check Mirage best content for United States right away, or after learning these important things about mirage.com
The Mirage, now owned and operated by Hard Rock International, brings you the best in entertainment, dining, hotel luxury and nightlife.
Visit mirage.comWe analyzed Mirage.com page load time and found that the first response time was 201 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mirage.com performance score
name
value
score
weighting
Value10.6 s
0/100
10%
Value26.2 s
0/100
25%
Value35.2 s
0/100
10%
Value33,440 ms
0/100
30%
Value0.567
12/100
15%
Value61.0 s
0/100
10%
201 ms
3218 ms
614 ms
711 ms
726 ms
Our browser made a total of 229 requests to load all elements on the main page. We found that 12% of them (28 requests) were addressed to the original Mirage.com, 4% (10 requests) were made to Pixel.rubiconproject.com and 4% (10 requests) were made to Static.mgmresorts.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Mirage.com.
Page size can be reduced by 1.7 MB (51%)
3.3 MB
1.6 MB
In fact, the total size of Mirage.com main page is 3.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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 137.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 137.2 kB or 72% of the original size.
Potential reduce by 25.9 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. Mirage images are well optimized though.
Potential reduce by 846.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 846.6 kB or 68% of the original size.
Potential reduce by 669.5 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. Mirage.com needs all CSS files to be minified and compressed as it can save up to 669.5 kB or 73% of the original size.
Number of requests can be reduced by 177 (87%)
204
27
The browser has sent 204 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mirage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and as a result speed up the page load time.
mirage.com
201 ms
en.html
3218 ms
index.css
614 ms
index.css
711 ms
jquery.js
726 ms
jquery.cookie.js
740 ms
session-me-helper.js
740 ms
session.js
791 ms
namespace.js
845 ms
session-me.js
933 ms
tealeaf_w3c_4_0_1067_07152015b.js
1021 ms
satelliteLib-0ef255248f6afb9ae6e6a55e457149fd220065d7.js
210 ms
Modernizr.js
1083 ms
require-config.js
1113 ms
require.js
2364 ms
me
411 ms
id
44 ms
mbox-contents-25cdb50b9490ebc766312d9e8ba3870f89f6d7d9.js
71 ms
satellite-54f4c17f3161370019ef0500.js
95 ms
satellite-5592fec8653866001700019f.js
93 ms
id
55 ms
target.js
46 ms
ajax
15 ms
trackingCode.js
153 ms
email_mlife.gif
1411 ms
geolocation
1300 ms
bestrates-banner_widget.png
1617 ms
mirage_map.png
2248 ms
best-rate-guarantee_footer.png
1555 ms
footer-aaa-four-diamond.png
1591 ms
footer-best-rate-guarantee.png
1902 ms
footer-green-key.png
2129 ms
arrows-footer-nav.png
205 ms
mlife-logo-sprite.svg
1187 ms
sprite-social.png
1162 ms
d5af76d8-a90b-4527-b3a3-182207cc3250.woff
1246 ms
9cfb0a83-d4a9-428e-a01e-92e075d6742a.woff
1245 ms
a0cf2f5e-c70c-45a8-a420-4143b3afb187.woff
1246 ms
4a9c62ab-b359-4081-8383-a0d1cdebd111.woff
1246 ms
b7a23f07-0f47-4c90-8e8f-f8962255c2a0.woff
1246 ms
8b105f29-73d5-4373-882d-bb4323e358c0.woff
1240 ms
11398868-5e58-467f-86d1-650e10dd998a.woff
1238 ms
loading-coin.gif
1168 ms
tag.js
23 ms
s-code-contents-4badffa7e7d0f619daef74d84e3ebe554c5e9745.js
1160 ms
checkTPC
93 ms
tag
33 ms
live.js
106 ms
tc.min.js
143 ms
mirage-attraction-volcano-lifestyle-genx-friends.tif.image.1440.550.high.jpg
930 ms
mirage-attractions-sgdh-hero-graphic-logo.tif.image.1440.550.high.jpg
1000 ms
mIrage-entertainment-love-stage-wide-confetti.tif.image.1440.550.high.jpg
929 ms
home.js
543 ms
json
57 ms
VideoViewer.js
187 ms
hit
113 ms
ca.html
179 ms
C7QRSUIGHJG5RGVQ6FOMMQ
178 ms
activity;src=3917468;type=corpe386;cat=corpm341;ord=1;prd=
156 ms
aquant.js
145 ms
x12091
135 ms
x11183
155 ms
activity;src=3917447;type=mirag539;cat=mirag726;ord=1;prd=
155 ms
ca.html
168 ms
ca.html
157 ms
ca.html
176 ms
o.js
435 ms
socialOptimizationPixel_js.php
171 ms
pixel;r=24088836;a=p-51fVpTbV0X0fw;ezt=1;orderid=;revenue=;labels=_fp.event.Mirage%20Homepage%2C_fp.channel.Mirage%2C_fp.channel.Mirage;fpan=1;fpa=P0-259967219-1456752265559;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456752265559;tzo=-180;ref=;url=https%3A%2F%2Fwww.mirage.com%2Fen.html;ogl=locale.en%2Ctitle.The%20Mirage%20Hotel%20%26%20Casino%20Las%20Vegas%20-%20English%2Cdescription.Welcome%20to%20where%20dreams%20come%20to%20play%252E%20Since%20day%20one%252C%20The%20Mirage%20has%20transformed%20%2Cimage.%2Curl.https%3A%2F%2Fwww%252Emirage%252Ecom%2Fen%252Ehtml
783 ms
Pug
783 ms
ibs:dpid=1121&dpuuid=769341484830767296&redir=
172 ms
cx
772 ms
rum
880 ms
adb.gif
678 ms
1
772 ms
cs
1207 ms
sync
773 ms
cs
1901 ms
adb.gif
758 ms
ibs:dpid=1121&dpuuid=785667034987348913&redir=
551 ms
1
760 ms
cx
761 ms
Pug
751 ms
sync
756 ms
cs
1231 ms
adb.gif
660 ms
ibs:dpid=1121&dpuuid=785667034987348912&redir=
589 ms
1
821 ms
cx
812 ms
Pug
818 ms
socialOptimizationPixel_js.php
537 ms
sync
744 ms
cs
1230 ms
adb.gif
742 ms
ibs:dpid=1121&dpuuid=785667034987348916&redir=
604 ms
1
797 ms
cx
849 ms
Pug
797 ms
s46790809580124
349 ms
satellite-558d9ef7633430001400010e.js
348 ms
0
686 ms
o
339 ms
count
636 ms
366738.gif
257 ms
ca.html
480 ms
fbevents.js
433 ms
ld.js
514 ms
360947.gif
220 ms
360947.gif
233 ms
360947.gif
245 ms
360947.gif
240 ms
satellite-55e769c36136640014000042.js
234 ms
pixel
236 ms
Pug
356 ms
cm
242 ms
cm
348 ms
cm
345 ms
xrefid.xgi
199 ms
367 ms
apid
415 ms
sd
209 ms
365 ms
401 ms
xrefid.xgi
196 ms
sd
270 ms
sync
196 ms
tap.php
193 ms
tap.php
192 ms
312 ms
xrefid.xgi
185 ms
lr.gif
318 ms
xrefid.xgi
173 ms
cm
230 ms
adxmapping.php
149 ms
tap.php
148 ms
lr.gif
266 ms
lr.gif
262 ms
lr.gif
259 ms
sd
136 ms
sd
137 ms
rum
151 ms
adxmapping.php
120 ms
rum
152 ms
relator
126 ms
mapuid
249 ms
satellite-562e9fc464746d2a4a0013b4.js
144 ms
tap.php
144 ms
sd
122 ms
rum
214 ms
cx
133 ms
tap.php
133 ms
cm
100 ms
generic
179 ms
rum
121 ms
cx
84 ms
1pix.gif
155 ms
rum
333 ms
src=4968412;type=invmedia;cat=rxp36zxe;ord=1
100 ms
xrefid.xgi
94 ms
92 ms
119 ms
pixel
105 ms
satellite-56621b1264746d7dbf0019ab.js
95 ms
tap.php
76 ms
Pug
76 ms
sd
52 ms
adb.gif
76 ms
1
75 ms
sync
74 ms
pixel
76 ms
362378.gif
75 ms
mapuser
57 ms
event
104 ms
socialOptimizationPixel_js.php
48 ms
29 ms
cm
31 ms
pixel
19 ms
satellite-56a9a56964746d0e45000ec1.js
108 ms
pixel
29 ms
ca.html
93 ms
oct.js
103 ms
adxmapping.php
33 ms
sd
38 ms
pixel
47 ms
tap.php
31 ms
Pug
67 ms
sd
23 ms
adb.gif
22 ms
1
30 ms
sync
21 ms
cs
180 ms
rum
98 ms
adsct
132 ms
adsct
122 ms
tre
17 ms
be5chn.js
91 ms
match
8 ms
Pix-1x1.gif
65 ms
src=4968412;type=invmedia;cat=iqkzmfz7;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1
62 ms
cm
36 ms
13 ms
ep
23 ms
ecc
60 ms
pixel
37 ms
pixel.gif
37 ms
cm
41 ms
epx.gif
33 ms
dis.aspx
113 ms
pixel
46 ms
161 ms
1
44 ms
match
111 ms
bind
157 ms
sync
162 ms
123
189 ms
tap.php
105 ms
match
155 ms
sync
49 ms
ad
203 ms
rtset
186 ms
Pug
126 ms
362338.gif
102 ms
set
140 ms
mapuser
46 ms
cookiematch.aspx
160 ms
tap.php
48 ms
tap.php
38 ms
px
30 ms
13 ms
mirage.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.
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
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
<frame> or <iframe> elements do not have a title
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.
mirage.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mirage.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
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 Mirage.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 Mirage.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.
mirage.com
Open Graph data is detected on the main page of Mirage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: