1.1 sec in total
74 ms
899 ms
159 ms
Welcome to fairmont.com homepage info - get ready to check Fairmont best content for United States right away, or after learning these important things about fairmont.com
Feel welcome to Fairmont luxury hotels and palaces. Book one of our rooms and enjoy exceptional comfort. Fairmont offers well-being spa, family or business stays through its meeting rooms.
Visit fairmont.comWe analyzed Fairmont.com page load time and found that the first response time was 74 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 20% of websites can load faster.
fairmont.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value9.1 s
1/100
25%
Value7.8 s
23/100
10%
Value2,490 ms
4/100
30%
Value0.371
29/100
15%
Value10.7 s
22/100
10%
74 ms
193 ms
26 ms
5 ms
20 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 50% of them (43 requests) were addressed to the original Fairmont.com, 7% (6 requests) were made to D1r80pgesjju2u.cloudfront.net and 6% (5 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (266 ms) belongs to the original domain Fairmont.com.
Page size can be reduced by 1.4 MB (45%)
3.1 MB
1.7 MB
In fact, the total size of Fairmont.com main page is 3.1 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 105.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 24.7 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 105.8 kB or 80% of the original size.
Potential reduce by 61.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. Fairmont images are well optimized though.
Potential reduce by 829.7 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 829.7 kB or 70% of the original size.
Potential reduce by 385.0 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. Fairmont.com needs all CSS files to be minified and compressed as it can save up to 385.0 kB or 79% of the original size.
Number of requests can be reduced by 39 (51%)
77
38
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fairmont. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
fairmont.com
74 ms
www.fairmont.com
193 ms
fairmont.min.css
26 ms
floating-widget.min.css
5 ms
s_code.js
20 ms
WebResource.axd
214 ms
WebResource.axd
9 ms
87b39ae1-4512-447a-8f3b-fad15f88e9c8.css
58 ms
jquery-1.7.min.js
16 ms
jquery-ui.min.js
8 ms
so_plugins.min.js
17 ms
fairmontfinal.min.js
18 ms
fairmontajax.min.js
4 ms
ip_Layer_Invitation_608.js
38 ms
dc.js
39 ms
gtm.js
28 ms
json
18 ms
593e534a-7cf8-4956-b5a9-4c8da07c3fa2.jpg
112 ms
9e85ce74-15ee-498a-93ad-2bb238145ef3.jpg
69 ms
f80962ba-47bc-4623-983a-fe3e7d242396.jpg
73 ms
10ba90e2-1468-4af2-a8d3-84677ff00a3f.jpg
249 ms
2a62bd40-e9cf-4a67-bc09-717b94faf167.jpg
14 ms
dc719390-018c-425f-b25d-ce551d37b44f.jpg
15 ms
d7795bf1-4857-426f-b7c7-4ae125d2a4e2.jpg
68 ms
6327e755-83f4-421c-b3a0-d961c839e327.jpg
69 ms
cbe89ea1-a340-4878-bd41-d695adcc916c.jpg
69 ms
5bef11f9-8d29-4c12-b9db-17948b5e3842.jpg
68 ms
43c4ab99-1825-4d82-b4f7-2de6181c1f81.jpg
111 ms
05ff010f-e6bd-4f72-94e4-3c69164be74d.jpg
109 ms
black.gif
151 ms
156c849c-c5aa-4b63-ad80-afc04f36b7a4.jpg
210 ms
01fd6b03-2a9b-474f-8355-bff68daac0fd.jpg
151 ms
d740ff42-9977-4e01-9ad0-86acbf7eef91.jpg
150 ms
4c5dda6d-21dd-413d-9c17-b7b08c7f330f.jpg
206 ms
74cc98f9-8fd9-404f-b318-27581064c526.jpg
208 ms
f7143ad5-c28b-4499-83d6-87fea9f2558e.jpg
208 ms
c0927bc8-765d-4094-837d-4009e399cb4c.jpg
208 ms
twitter.gif
212 ms
facebook.gif
244 ms
youtube.gif
245 ms
rss.gif
209 ms
pinterest.gif
211 ms
instagram1.gif
211 ms
98ac98d2-f10a-4a96-8238-b196a8b43810.gif
244 ms
1780284c-cccb-4770-a04b-18877c4b26c7.png
266 ms
loading_fairmont.gif
244 ms
d3d8333c-88d8-475c-ad65-0a9e5d79f97e.jpg
252 ms
conversion_async.js
92 ms
analytics.js
90 ms
1881
190 ms
fbds.js
185 ms
oct.js
86 ms
p-sW3094j8bNYXU.gif
87 ms
sessioncam.recorder.js
126 ms
__utm.gif
87 ms
brandnav-arrow.png
211 ms
expand2.png
145 ms
subscribe.png
212 ms
08fe22ab-0517-4203-bcc9-1ba2ca45f40c.woff
101 ms
6c1059a5-93a4-4c07-8464-8ee5df381c36.woff
142 ms
10ab5970-5726-4843-82b1-912faa9307ff.woff
142 ms
41c174b1-68c1-41b7-a19f-5ec80929b115.woff
141 ms
119 ms
linkid.js
71 ms
ec.js
72 ms
adsct
155 ms
adsct
104 ms
ga-audiences
142 ms
Layer_Global_aicollect_2012.js
96 ms
processing.aspx
231 ms
geotarget.ashx
179 ms
ui-bg_flat_100_ffffff_40x100.png
210 ms
s46707945077214
41 ms
config.aspx
103 ms
137 ms
collect
86 ms
collect
103 ms
src=4831742;type=sales;cat=lhmomabl;qty=1;cost=0;u1=[cid];u16=[pc];ord=[OrderID]
130 ms
pixel
106 ms
67 ms
Layer_608.js
41 ms
invitation1_fairmont.png
161 ms
counter_N.png
47 ms
AdX
65 ms
eb75551b-2adf-4806-994e-2f24d12ac9d3.jpg
69 ms
22 ms
fairmont.com accessibility score
fairmont.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fairmont.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 Fairmont.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 Fairmont.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.
fairmont.com
Open Graph description is not detected on the main page of Fairmont. 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: