3.2 sec in total
140 ms
2.5 sec
612 ms
Welcome to clarkhotels.com homepage info - get ready to check Clark Hotels best content right away, or after learning these important things about clarkhotels.com
Visit clarkhotels.comWe analyzed Clarkhotels.com page load time and found that the first response time was 140 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
clarkhotels.com performance score
140 ms
52 ms
87 ms
60 ms
65 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Clarkhotels.com, 39% (40 requests) were made to Static.parastorage.com and 27% (28 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.1 MB (53%)
5.8 MB
2.7 MB
In fact, the total size of Clarkhotels.com main page is 5.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 108.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. 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 108.8 kB or 83% of the original size.
Potential reduce by 44.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. Clark Hotels images are well optimized though.
Potential reduce by 2.7 MB
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 2.7 MB or 77% of the original size.
Potential reduce by 193.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. Clarkhotels.com needs all CSS files to be minified and compressed as it can save up to 193.9 kB or 85% of the original size.
Number of requests can be reduced by 62 (65%)
95
33
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clark Hotels. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
clarkhotels.com
140 ms
www.clarkhotels.com
52 ms
bt
87 ms
require.min.js
60 ms
main-r.min.js
65 ms
viewer.css
57 ms
dynamicmodel
29 ms
3ed7c9_f03f1f6364387e7b6039dfd6c2089565_176.json.z
464 ms
3ed7c9_4cf966a21c3f5dd13a7b8cd0c8850468_176.json.z
501 ms
ugc-viewer
38 ms
bt
149 ms
skins.min.js
151 ms
components.min.js
53 ms
utils.min.js
52 ms
core.min.js
136 ms
react-with-addons.min.js
137 ms
lodash.min.js
33 ms
TweenMax.min.js
139 ms
layout.min.js
132 ms
tpa.min.js
137 ms
fonts.min.js
136 ms
animations.min.js
132 ms
swfobject.min.js
135 ms
mousetrap.min.js
134 ms
tweenEngine.min.js
137 ms
DrawSVGPlugin.min.js
137 ms
react-dom.min.js
134 ms
ScrollToPlugin.min.js
135 ms
widgets.min.js
133 ms
experiment.js
141 ms
render.min.js
141 ms
wixappsCore.min.js
137 ms
wixappsClassics.min.js
142 ms
wixappsBuilder.min.js
135 ms
zepto.min.js
138 ms
color.min.js
135 ms
react-dom-server.min.js
73 ms
bt
178 ms
bt
46 ms
f3e0fce3efa148a7aad30ae8507dd967.svg
5 ms
dc.js
369 ms
bt
345 ms
apple_box.png
186 ms
css
182 ms
latin.css
179 ms
3ed7c9_30aea7fcfaf349c904597d8d459f02e2.html
249 ms
Thumbnails.html
191 ms
widget.aspx
598 ms
3ed7c9_3e78814536574e58b58f9d7e40a57a07.png
431 ms
3ed7c9_66e84aa922fd4997a3e5ef93f1790053.png
329 ms
9c608a_22f05971db3547a49008d4aa9f74260c.png
315 ms
3ed7c9_1d72dbaa98904aef90bd37428e5e60bb.png
439 ms
3ed7c9_baef4bc4a1a1467cad4fc2a0e1afa185.png
1234 ms
3ed7c9_03adfaae86084b8ab69eedb0cf6b8ac1.jpg
432 ms
3ed7c9_960296a1367649a9bf7481a28b6dc037.jpg
494 ms
3ed7c9_4fa4d9894e624e97877240658c99ed08.jpg
1238 ms
3ed7c9_9b704ea200674233abc7b99adb6a705f.png
1239 ms
3ed7c9_bd760e7b294647d48ee93cef2d6619d5.jpg
1239 ms
3ed7c9_598df9bd6da245efa6ebfe53f4794e26.jpg
1239 ms
6282e125651246cf8362f57d8d5a9b67.jpg
509 ms
bt
152 ms
bt
151 ms
jquery.min.js
125 ms
lodash.min.js
277 ms
webfont.js
315 ms
Wix.js
283 ms
style.min.css
123 ms
app.min.js
120 ms
__utm.gif
55 ms
8fb1090e-b4d0-4685-ac8f-3d0c29d60130.woff
46 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
46 ms
Pqd6s-RedeRT8zQTRwM-ug.woff
47 ms
ga-audiences
308 ms
wejs
266 ms
150_logo-11900-2.png
198 ms
ugc-viewer
115 ms
css
156 ms
analytics.js
764 ms
jquery.min.js
75 ms
Wix.js
93 ms
angular.js
138 ms
widgetWix.js
103 ms
arrow-left.png
60 ms
3ed7c9_c7e96bdcac4943ff8707b00dc4e73be3.jpg
748 ms
3ed7c9_17a33d8dd0564067b3c3fa0381771952.jpg
749 ms
3ed7c9_cf8037b7a05b433aa37395c63f55b9f5.jpg
748 ms
3ed7c9_bd760e7b294647d48ee93cef2d6619d5.jpg
749 ms
3ed7c9_4398089e78e84da684ec2ce26d6001c0.jpg
750 ms
3ed7c9_598df9bd6da245efa6ebfe53f4794e26.jpg
751 ms
3ed7c9_960296a1367649a9bf7481a28b6dc037.jpg
751 ms
3ed7c9_894293222f0a465fba11aec637d24585.jpg
752 ms
3ed7c9_257e6fa6a2444171a252091740192bf9.jpg
753 ms
3ed7c9_a769ba0796fc42ae9169375d1fd42271.jpg
752 ms
3ed7c9_773db47a824641c1b5cb8fb1c4cf7113.jpg
752 ms
3ed7c9_35c6e755150041c1a93756b8c6f71d8d.jpg
782 ms
arrow-right.png
43 ms
6282e125651246cf8362f57d8d5a9b67.jpg
694 ms
WidgetEmbed-selfserveprop
665 ms
bontact.script.js
55 ms
collect
45 ms
cdswidSSP-v2414594452a.css%20%27%29%3B
22 ms
cdswidgets_m-c-v2102084671a.js
49 ms
cdswidSSP-v2414594452a.css
26 ms
clarkhotels.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Clarkhotels.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Clarkhotels.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.
clarkhotels.com
Open Graph description is not detected on the main page of Clark Hotels. 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: