4.9 sec in total
1.1 sec
3.2 sec
651 ms
Visit spatial.ly now to see the best up-to-date Spatial content for United States and also check out these interesting facts you probably never knew about spatial.ly
Spatial Analysis, Visualisation and Resources
Visit spatial.lyWe analyzed Spatial.ly page load time and found that the first response time was 1.1 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
spatial.ly performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
1100 ms
410 ms
178 ms
182 ms
23 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 44% of them (59 requests) were addressed to the original Spatial.ly, 19% (26 requests) were made to Pbs.twimg.com and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Spatial.ly.
Page size can be reduced by 833.7 kB (22%)
3.8 MB
3.0 MB
In fact, the total size of Spatial.ly main page is 3.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. 75% 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 60.4 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 60.4 kB or 81% of the original size.
Potential reduce by 202.4 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. Spatial images are well optimized though.
Potential reduce by 254.3 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 254.3 kB or 62% of the original size.
Potential reduce by 316.6 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. Spatial.ly needs all CSS files to be minified and compressed as it can save up to 316.6 kB or 83% of the original size.
Number of requests can be reduced by 56 (44%)
126
70
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spatial. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
spatial.ly
1100 ms
style.css
410 ms
related-posts.css
178 ms
twitter-feed.css
182 ms
css
23 ms
css
14 ms
wpp.css
170 ms
shortcodes.css
428 ms
shortcodes_responsive.css
190 ms
jquery.fancybox-1.3.4.css
195 ms
page_templates.css
363 ms
jquery.js
717 ms
jquery-migrate.min.js
287 ms
share.js
5 ms
show_ads.js
5 ms
superfish.js
132 ms
jquery.flexslider-min.js
236 ms
jquery.fitvids.js
182 ms
custom.js
262 ms
jquery.easing-1.3.pack.js
189 ms
jquery.fancybox-1.3.4.pack.js
265 ms
et-ptemplates-frontend.js
269 ms
wp-emoji-release.min.js
157 ms
ga.js
62 ms
sdk.js
180 ms
shadow.png
114 ms
twitter.png
117 ms
rss.png
117 ms
search_btn.png
112 ms
spatially_logo_2line-01.png
373 ms
print_sale-960x355.png
1211 ms
info_cap_spally_banner-960x355.jpg
461 ms
pop_lines_banner-960x355.jpg
622 ms
journey_to_work_web-960x360.gif
736 ms
Screenshot-2014-06-17-16.02.07-960x360.png
1420 ms
more-arrow.png
453 ms
shadow2.png
565 ms
hurricanes-37x37.jpg
572 ms
colour_votes_jcheshire-37x37.jpg
689 ms
journey_to_work_web-742655_37x37.gif
687 ms
r-BURGER-MAP-large570-37x37.jpg
709 ms
datashine_new_features-37x37.png
717 ms
Screenshot-2014-06-17-16.02.07-37x37.png
730 ms
spatial_ggplot2-37x37.png
792 ms
commute_flows_before_after-37x37.jpg
799 ms
pacific-ranges-37x37.jpg
819 ms
middle-shadow.png
825 ms
NATS_24_hrs-136x77.jpg
875 ms
video_play_arrow.png
880 ms
Screen-Shot-2013-11-22-at-11.35.33-136x77.png
996 ms
monatge_422-136x77.png
922 ms
next_spill-136x77.png
965 ms
hurricanes-128x128.jpg
966 ms
colour_votes_jcheshire-128x128.jpg
1012 ms
journey_to_work_web-742655_128x128.gif
1087 ms
r-BURGER-MAP-large570-128x128.jpg
1086 ms
print_sale-128x128.png
1177 ms
info_cap_osm-128x128.jpg
1108 ms
JC_head_sml_BW-81038_74x74.png
1128 ms
asia.png
1541 ms
widgets.js
48 ms
TheInformationCapital_cover_500px.jpg
1474 ms
_EWOrZQ3L-c
186 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
66 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
71 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
106 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
105 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
105 ms
zrt_lookup.html
304 ms
show_ads_impl.js
93 ms
__utm.gif
32 ms
widget-blue-bullet.png
1104 ms
rss.png
1155 ms
ads
373 ms
osd.js
167 ms
left-arrow.png
973 ms
right-arrow.png
975 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
83 ms
242 ms
xd_arbiter.php
200 ms
xd_arbiter.php
346 ms
rJC7B-9ZfhE
69 ms
_EWOrZQ3L-c
176 ms
X9UtUzHDn4c
96 ms
syndication
176 ms
327387211291049984
477 ms
www-embed-player-vflfNyN_r.css
11 ms
www-embed-player.js
41 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
78 ms
ad_status.js
80 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
70 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
76 ms
m_js_controller.js
41 ms
abg.js
55 ms
favicon
69 ms
googlelogo_color_112x36dp.png
76 ms
nessie_icon_tiamat_white.png
55 ms
s
36 ms
x_button_blue2.png
23 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
4 ms
proxy.jpg
37 ms
proxy.jpg
19 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
13 ms
Fsb0viMz_normal.jpeg
148 ms
QfPmIIHG_normal.jpeg
169 ms
W7sZz155_normal.png
200 ms
UHzJaluX_normal.png
232 ms
eHFIwyHu_normal.jpg
249 ms
117b8b681231f1e7ddfa7e4da563709c_normal.jpeg
265 ms
jWklxl4i_normal.jpg
261 ms
2009_MarkYosemite_normal.jpg
263 ms
pM-GjWcL_normal.jpg
263 ms
_Ss_u6L-_normal.jpg
269 ms
IMG_2390_normal.JPG
276 ms
fNP8Aazg_normal.png
292 ms
MudLFJqh_normal.png
290 ms
grRiEWpI_normal.jpeg
289 ms
CdmADMMWEAAZvb5.jpg:small
286 ms
CdCiGOSW8AEHg3F.jpg:small
295 ms
CcpOuQ_W4AAaBgV.jpg:small
301 ms
CcjSA2uWoAAWLIw.jpg:small
314 ms
Ccbi47AUAAAC53Y.jpg:small
320 ms
CcirX2DWAAAFW2P.jpg:small
318 ms
CbwocVpW0AIiOcK.jpg:small
340 ms
CbViaK0WAAEFe-W.jpg:small
320 ms
Ca3FtvKUUAAXMiA.jpg:small
327 ms
CatL1wHUsAENegu.jpg:small
337 ms
Cbp8H9CWEAA369L.jpg:small
343 ms
Cbp8H9PWwAE-mLa.jpg:small
344 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
42 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
52 ms
proxy.jpg
10 ms
proxy.jpg
6 ms
jot.html
3 ms
spatial.ly accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
spatial.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
spatial.ly SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spatial.ly 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 Spatial.ly 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.
spatial.ly
Open Graph data is detected on the main page of Spatial. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: