862 ms in total
35 ms
501 ms
326 ms
Visit walltime.nyc now to see the best up-to-date Walltime content and also check out these interesting facts you probably never knew about walltime.nyc
Walltime™ is a unique new way to share Vimeo and YouTube videos, through light projections on massive walls in New York City.
Visit walltime.nycWe analyzed Walltime.nyc page load time and found that the first response time was 35 ms and then it took 827 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
walltime.nyc performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value12.4 s
0/100
25%
Value13.8 s
1/100
10%
Value1,570 ms
13/100
30%
Value0
100/100
15%
Value23.2 s
1/100
10%
35 ms
57 ms
69 ms
10 ms
32 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Walltime.nyc, 32% (12 requests) were made to Use.typekit.net and 27% (10 requests) were made to Assets.squarespace.com. The less responsive or slowest element that took the longest time to load (329 ms) relates to the external source Images.squarespace-cdn.com.
Page size can be reduced by 65.2 kB (4%)
1.6 MB
1.5 MB
In fact, the total size of Walltime.nyc main page is 1.6 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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 60.0 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.0 kB or 78% of the original size.
Potential reduce by 589 B
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. Walltime images are well optimized though.
Potential reduce by 4.7 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 15 (65%)
23
8
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Walltime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
www.walltime.nyc
35 ms
CG9pMcQb-C_vuswUab-YlVxdpufIgKvij5_Fvt_pjDwfelqffFHN4UJLFRbh52jhWD9twQ6oFDyKwQqajAmywAIoFewkjDJXFU7IMPG0ihBCdYsTdA9ld18RO1FUiABkZWF3jAF8OcFzdPUCdhFydeyzSabCihBCdYsTdA9ld18RO1FUiABkZWF3jAF8OcFzdPUajAUCie8lZPo0pAwCiaiaO1iydeUX-Au8OAoojkoDSWmyScmDSeBRZPoRdhXCiaiaO1iydeUX-Au8OcoojkJwSY4zpe8ljPu0daZyJyBy-asTiKu1ScNXZWFnOWFXZfJ4Z1mXiW4yOWgXH6qJtKGbMg62JMJ7fbKzMsMMeMb6MKGHfO2IMsMMeM96MKG4fJCgIMMjgkMfH6qJtkGbMg6FJMJ7fbK3MsMMeMt6MKG4fJ3gIMMjIPMfH6qJXcXbMs6YJMJ7fbKImsMfeMb6MKG4fJBmIMJjgkMfH6qJ689bMy6sJMHbMZHzuCtB.js
57 ms
css2
69 ms
legacy.js
10 ms
modern.js
32 ms
extract-css-runtime-a1e649c3a5b9974bbb39-min.en-US.js
32 ms
extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js
32 ms
cldr-resource-pack-f4df7777522f8adb8991-min.en-US.js
32 ms
common-vendors-stable-61293f01d648eef165fc-min.en-US.js
32 ms
common-vendors-8185067acd9ec156c0b5-min.en-US.js
31 ms
common-6b6165b16e38955f7fd1-min.en-US.js
54 ms
performance-811237e1adfb0a5866e3-min.en-US.js
44 ms
site.css
66 ms
jquery.min.js
59 ms
js
202 ms
widgets.js
43 ms
site-bundle.js
59 ms
analytics.js
126 ms
iPhone-7-Plus-with-earbuds.jpg
329 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
94 ms
d
67 ms
d
80 ms
d
94 ms
d
93 ms
HurmeSemiBold.otf
48 ms
squarespace-ui-font.svg
64 ms
HurmeRegular.otf
48 ms
d
103 ms
d
104 ms
d
94 ms
d
105 ms
d
104 ms
d
103 ms
d
103 ms
p.gif
61 ms
collect
32 ms
js
44 ms
walltime.nyc accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
walltime.nyc 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
walltime.nyc SEO score
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 Walltime.nyc 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 Walltime.nyc 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.
walltime.nyc
Open Graph data is detected on the main page of Walltime. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: