19.2 sec in total
5.8 sec
13.2 sec
237 ms
Welcome to 501places.com homepage info - get ready to check 501 Places best content for India right away, or after learning these important things about 501places.com
Travel blog of Andy Jarosz, Freelance Travel Writer. Listed in Top 50 Travel Websites by The Times and The Independent.
Visit 501places.comWe analyzed 501places.com page load time and found that the first response time was 5.8 sec and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
501places.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value4.5 s
36/100
25%
Value2.8 s
96/100
10%
Value770 ms
38/100
30%
Value0
100/100
15%
Value7.8 s
45/100
10%
5799 ms
1198 ms
31 ms
1230 ms
1331 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 49% of them (31 requests) were addressed to the original 501places.com, 16% (10 requests) were made to Static.xx.fbcdn.net and 14% (9 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain 501places.com.
Page size can be reduced by 251.3 kB (45%)
563.3 kB
311.9 kB
In fact, the total size of 501places.com main page is 563.3 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. 45% of websites need less resources to load. Javascripts take 235.6 kB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 5.9 kB, which is 13% 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 35.1 kB or 80% of the original size.
Potential reduce by 12.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. 501 Places images are well optimized though.
Potential reduce by 145.1 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 145.1 kB or 62% of the original size.
Potential reduce by 59.1 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. 501places.com needs all CSS files to be minified and compressed as it can save up to 59.1 kB or 85% of the original size.
Number of requests can be reduced by 23 (37%)
62
39
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 501 Places. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.501places.com
5799 ms
style.css
1198 ms
jquery.min.js
31 ms
jquery.cycle.min.js
1230 ms
jquery.js
1331 ms
jquery-migrate.min.js
1246 ms
superfish.js
1213 ms
general.js
1292 ms
tw-sack.min.js
1315 ms
default.css
1315 ms
shortcodes.css
1313 ms
custom.css
1312 ms
wp-embed.min.js
1380 ms
wp-emoji-release.min.js
177 ms
ga.js
27 ms
__utm.gif
96 ms
analytics.js
34 ms
b69112e8a90953f91b56dabd2e158f0d
246 ms
501-sm2.png
247 ms
ico-rssfeed.png
248 ms
ico-twitter.png
247 ms
ico-stumbleupon.png
248 ms
ico-facebook.png
248 ms
Presentation4-281x150.jpg
249 ms
thumb.php
866 ms
thumb.php
866 ms
thumb.php
793 ms
thumb.php
813 ms
thumb.php
740 ms
thumb.php
829 ms
thumb.php
1178 ms
thumb.php
1395 ms
thumb.php
1374 ms
all.js
281 ms
bg-scanlines.png
895 ms
ico-search.png
925 ms
widgets.js
220 ms
collect
183 ms
arrow-superfish.png
877 ms
54 ms
xd_arbiter.php
211 ms
xd_arbiter.php
415 ms
ping
38 ms
like_box.php
110 ms
NR0nFiTsKtx.css
284 ms
7I4WHfGTXwv.css
350 ms
_rx8naC75Dy.js
491 ms
x5F9OMjKyLw.js
617 ms
ICDbTSzjQEg.js
485 ms
TTCre3391I0.js
490 ms
430300_10150631173034755_1720943696_n.jpg
41 ms
46149_419991229754_6609849_n.jpg
38 ms
10703605_593843264059168_4360582299502838715_n.jpg
40 ms
182329_103384586499308_1612582036_n.jpg
41 ms
10437601_706554949409370_1113942094916089059_n.jpg
41 ms
12510403_810185519127845_7556450655177767253_n.jpg
41 ms
12249956_1526222344363729_8824153455360779143_n.jpg
41 ms
12745875_10205972543489549_8488540470049738067_n.jpg
42 ms
7353_560801457358366_4291473053143801899_n.jpg
43 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
73 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
136 ms
501places.com accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
501places.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
Browser errors were logged to the console
501places.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 501places.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 501places.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.
501places.com
Open Graph description is not detected on the main page of 501 Places. 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: