8.5 sec in total
98 ms
2.8 sec
5.6 sec
Click here to check amazing Likecube content. Otherwise, check out these important facts you probably never knew about likecube.com
Your ultimate guide to the best art and entertainment, food and drink, attractions, hotels and things to do in the world’s greatest cities.
Visit likecube.comWe analyzed Likecube.com page load time and found that the first response time was 98 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.
likecube.com performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value10.5 s
0/100
25%
Value9.6 s
11/100
10%
Value10,550 ms
0/100
30%
Value0.049
99/100
15%
Value30.4 s
0/100
10%
98 ms
237 ms
222 ms
28 ms
51 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Likecube.com, 12% (14 requests) were made to Timeout.com and 4% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Media.timeout.com.
Page size can be reduced by 400.4 kB (5%)
7.9 MB
7.5 MB
In fact, the total size of Likecube.com main page is 7.9 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. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 250.1 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 250.1 kB or 89% of the original size.
Potential reduce by 81.6 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. Likecube images are well optimized though.
Potential reduce by 68.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 68.6 kB or 39% of the original size.
Potential reduce by 138 B
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. Likecube.com has all CSS files already compressed.
Number of requests can be reduced by 26 (23%)
114
88
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Likecube. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
www.timeout.com
98 ms
optimize.js
237 ms
gtm.js
222 ms
main-a5f6d3a59146ea14a19a565f464b7539.css
28 ms
cityhome-b6f8866960c22a57e6284d04917bd756.css
51 ms
store-07c7f056a3b21121fae6.js
81 ms
cmp-f6482ef9321b9886e21f.js
81 ms
permutive-871b990eb66e4f6c1474.js
181 ms
67cbf6c5-d926-407b-a684-a0606570ff08-web.js
540 ms
11092.js
803 ms
gpt.js
541 ms
visitor-api-816c7e93e3b33c46c4afdcec86bc669d.js
71 ms
satelliteLib-471155aab562061e30b42d5636aaa36d2a4d9195.js
368 ms
ads-45387acd2f642d53df5c.js
174 ms
libs-d35057a2d9196a9a7934.js
172 ms
app-measurement-4f373f071520eda2e203f2e0fa3941c0.js
311 ms
banner
799 ms
main-6955436e983d541ad6b7.js
310 ms
auto-complete-652f4a32370eb0295674f4a8e38f4d3b.js
309 ms
events.js
823 ms
image.jpg
736 ms
hotjar-380860.js
707 ms
image.jpg
741 ms
image.jpg
1018 ms
image.jpg
1017 ms
image.jpg
1019 ms
image.jpg
1018 ms
image.jpg
1017 ms
image.jpg
1015 ms
image.jpg
1039 ms
image.jpg
1060 ms
image.jpg
1059 ms
image.jpg
1048 ms
image.jpg
1058 ms
image.jpg
1034 ms
image.jpg
1062 ms
image.jpg
1062 ms
image.jpg
1160 ms
image.jpg
1065 ms
image.jpg
1062 ms
image.jpg
1065 ms
image.jpg
1119 ms
image.jpg
1120 ms
image.jpg
1114 ms
image.jpg
1119 ms
image.jpg
1119 ms
image.jpg
1138 ms
image.jpg
1141 ms
image.jpg
1142 ms
image.jpg
1138 ms
image.jpg
1139 ms
image.jpg
1164 ms
image.jpg
1149 ms
image.jpg
1151 ms
image.jpg
1163 ms
image.jpg
1160 ms
image.jpg
1163 ms
location-search-bg.jpeg
660 ms
logo.png
321 ms
gtm.js
254 ms
RC172250ad878b40cbaf836eac7f1143e4-source.min.js
314 ms
RC3fa63cac290741f7a11fa4c0b2db236c-source.min.js
357 ms
RC572aeebfa865486e91f7b21c914a2e20-source.min.js
355 ms
pubads_impl_2022092001.js
295 ms
ppub_config
548 ms
analytics.js
471 ms
js
133 ms
image.jpg
493 ms
modules.01a02f6e8b126e8c8358.js
498 ms
image.jpg
447 ms
rd
303 ms
image.jpg
172 ms
image.jpg
179 ms
image.jpg
174 ms
image.jpg
174 ms
image.jpg
177 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
248 ms
image.jpg
157 ms
image.jpg
193 ms
image.jpg
200 ms
dest5.html
221 ms
id
189 ms
image.jpg
186 ms
image.jpg
189 ms
image.jpg
189 ms
image.jpg
186 ms
image.jpg
180 ms
image.jpg
199 ms
image.jpg
200 ms
image.jpg
194 ms
image.jpg
194 ms
collect
94 ms
collect
46 ms
collect
48 ms
image.jpg
132 ms
image.jpg
135 ms
image.jpg
140 ms
image.jpg
152 ms
image.jpg
147 ms
image.jpg
132 ms
image.jpg
138 ms
image.jpg
136 ms
image.jpg
138 ms
image.jpg
134 ms
image.jpg
134 ms
image.jpg
134 ms
image.jpg
122 ms
image.jpg
123 ms
image.jpg
122 ms
image.jpg
127 ms
image.jpg
124 ms
collect
119 ms
ibs:dpid=411&dpuuid=YzH4QQAAAMZCGANw
39 ms
ga-audiences
40 ms
collect
7 ms
likecube.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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
likecube.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
likecube.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Likecube.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 Likecube.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.
likecube.com
Open Graph data is detected on the main page of Likecube. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: