10 sec in total
322 ms
5.9 sec
3.8 sec
Click here to check amazing C360 content for Netherlands. Otherwise, check out these important facts you probably never knew about c360.nl
Visit c360.nlWe analyzed C360.nl page load time and found that the first response time was 322 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
c360.nl performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value6.6 s
8/100
25%
Value8.5 s
18/100
10%
Value1,890 ms
9/100
30%
Value0
100/100
15%
Value17.1 s
4/100
10%
322 ms
22 ms
790 ms
3 ms
6 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 20% of them (26 requests) were addressed to the original C360.nl, 18% (23 requests) were made to Maps.googleapis.com and 13% (16 requests) were made to 360cities.net. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Iloapp.c360.nl.
Page size can be reduced by 3.0 MB (31%)
10.0 MB
6.9 MB
In fact, the total size of C360.nl main page is 10.0 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 6.0 MB which makes up the majority of the site volume.
Potential reduce by 306 B
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 306 B or 41% of the original size.
Potential reduce by 319.8 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. C360 images are well optimized though.
Potential reduce by 2.3 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.3 MB or 67% of the original size.
Potential reduce by 430.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. C360.nl needs all CSS files to be minified and compressed as it can save up to 430.6 kB or 83% of the original size.
Number of requests can be reduced by 57 (51%)
112
55
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of C360. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
c360.nl
322 ms
wrapper.js
22 ms
www
790 ms
default.css
3 ms
template1_purple.css
6 ms
1394748747blogadmin.css
272 ms
blog.js
13 ms
DutchVRDays_stand_c360_s.jpg
785 ms
9k=
13 ms
www
202 ms
www
1556 ms
www
1452 ms
thumbnail.jpg
1225 ms
Z
16 ms
9k=
13 ms
BHVD_360.jpg
633 ms
rss.gif
11 ms
ISA_p.jpg
692 ms
ASML_p.jpg
691 ms
goghmile_p.jpg
1060 ms
vgm_photo.jpg
795 ms
mbain1dag_550.jpg
692 ms
MW_pinnedup.png
1303 ms
Passage_lps.jpg
962 ms
BBBQ.png
2932 ms
Spot4_LP_s.jpg
793 ms
Pegman_RAI.jpg
972 ms
boom.png
3376 ms
preview_s.png
1458 ms
vanmoof.png
3377 ms
5concerten.jpg
1302 ms
stedelijk12.jpg
1459 ms
moooi_milan.jpg
1458 ms
www
104 ms
www
3871 ms
www
1458 ms
cellphone-icon.png
10 ms
maps
52 ms
maps
72 ms
658 ms
quai-rambaud
94 ms
749 ms
745 ms
embed
53 ms
share-background.png
17 ms
arrow.gif
4 ms
kMWxBpM-MSA
82 ms
embed
78 ms
embed
34 ms
js
89 ms
init_embed.js
36 ms
embed_iframe.js
38 ms
embed_iframe.css
47 ms
js
29 ms
embed_iframe_async.js
264 ms
js
114 ms
init_embed.js
32 ms
www-embed-player-vflfNyN_r.css
128 ms
www-embed-player.js
211 ms
base.js
341 ms
font-awesome.min.css
104 ms
soc_icn_fb.png
104 ms
soc_icn_twitter.png
105 ms
soc_icn_gp.png
141 ms
soc_icn_mail.png
141 ms
soc_icn_pin.png
140 ms
icon_editorial.png
140 ms
icon_video.png
139 ms
icon_mobile.png
199 ms
fontello.css
212 ms
css
268 ms
common.js
77 ms
util.js
68 ms
streetview.js
99 ms
google_white4.png
67 ms
marker.js
117 ms
imagery_viewer.js
81 ms
controls.js
27 ms
GeoPhotoService.GetMetadata
239 ms
transparent.png
204 ms
css
212 ms
geocoder.js
172 ms
sv4.png
180 ms
openhand_8_8.cur
177 ms
diag_line_2.png
173 ms
diag_line_1.png
172 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
85 ms
ad_status.js
184 ms
mapcnt6.png
85 ms
tmapctrl.png
85 ms
common.js
78 ms
util.js
79 ms
streetview.js
79 ms
analytics.js
149 ms
b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff
315 ms
Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff
315 ms
b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff
315 ms
fontello.woff
148 ms
GeoPhotoService.GetMetadata
294 ms
VM.js
365 ms
swfkrpano.js
270 ms
swfkrpano.js
267 ms
marker.js
405 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
146 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
365 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
371 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
371 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
383 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
383 ms
imagery_viewer.js
349 ms
controls.js
325 ms
cbk
489 ms
GeoPhotoService.GetMetadata
315 ms
collect
240 ms
GeoPhotoService.GetMetadata
348 ms
get_flash_player.gif
405 ms
GeoPhotoService.GetMetadata
234 ms
GeoPhotoService.GetMetadata
231 ms
cbk
178 ms
geocoder.js
90 ms
cbk
1538 ms
cbk
2035 ms
cbk
2033 ms
cbk
1532 ms
GeoPhotoService.GetMetadata
825 ms
cbk
1709 ms
cbk
1708 ms
cbk
942 ms
c360.nl accessibility score
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
<frame> or <iframe> elements do not have a title
c360.nl 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
Missing source maps for large first-party JavaScript
c360.nl SEO score
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
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise C360.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 C360.nl 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.
c360.nl
Open Graph description is not detected on the main page of C360. 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: