3 sec in total
37 ms
1.8 sec
1.2 sec
Click here to check amazing Density content for United States. Otherwise, check out these important facts you probably never knew about density.io
Density shows you how people use your space and helps you improve your workplace ROI.
Visit density.ioWe analyzed Density.io page load time and found that the first response time was 37 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
density.io performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value6.4 s
10/100
25%
Value7.9 s
23/100
10%
Value3,490 ms
2/100
30%
Value0.026
100/100
15%
Value19.1 s
3/100
10%
37 ms
1107 ms
112 ms
147 ms
91 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Density.io, 46% (32 requests) were made to Cdn.prod.website-files.com and 16% (11 requests) were made to Assets.website-files.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Density.io.
Page size can be reduced by 2.2 MB (15%)
15.2 MB
12.9 MB
In fact, the total size of Density.io main page is 15.2 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. Only a small number of websites need less resources to load. Images take 14.6 MB which makes up the majority of the site volume.
Potential reduce by 67.6 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 67.6 kB or 80% of the original size.
Potential reduce by 2.2 MB
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. Obviously, Density needs image optimization as it can save up to 2.2 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 45 B
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.
Potential reduce by 0 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. Density.io has all CSS files already compressed.
Number of requests can be reduced by 13 (28%)
46
33
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Density. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
density.io
37 ms
www.density.io
1107 ms
density.6a7e129bf.min.css
112 ms
vyt4lzl.js
147 ms
otSDKStub.js
91 ms
optimize.js
141 ms
gsap.min.js
90 ms
ScrollTrigger.min.js
92 ms
jquery-3.5.1.min.js
79 ms
gsap.min.js
85 ms
ScrollTrigger.min.js
88 ms
v2.js
138 ms
jquery-3.5.1.min.dc5e7f18c8.js
82 ms
density.59851f9ea.js
137 ms
ScrollTrigger.min.js
80 ms
gsap.min.js
32 ms
391b672c-a685-4952-b92a-b6ac11f9507c-test.json
216 ms
gtm.js
299 ms
654aa13e6d8d52d11a9f157a_login%20icon.svg
209 ms
653ad08d0d2d7e490dcb745e_white%20arrow.svg
41 ms
654294680d9181c689502378_arrow-right%2C%20forward_carbono.svg
57 ms
654281fbe902a1a8ddf26662_share%20metrics%20image.png
62 ms
651b2df59322b21715eeba4c_calendar.svg
57 ms
651b2df4c67661b7180736fa_average%20time.svg
75 ms
651b2df4cbd222e343552941_average.svg
79 ms
651b2df5ca92a5fded8d60f3_heatmap.png
99 ms
654aaf6633a0dbd73180d5c8_dashboard.png
102 ms
651b2df503633ac450444c71_occupancy.svg
77 ms
651b2df520b966440a6d77d7_amenities.svg
93 ms
651b338985302338f520bfd2_utilization.svg
100 ms
651b2df5fbbe7cefe1555d1a_rooms.png
133 ms
6515cbf38b89ba6e33444322_insights%20graph_2.png
130 ms
651b2df406a26d341d6fab27_Observations.svg
137 ms
6537e870df814fdab0c957f3_home_left%20shapes.png
130 ms
653ad34997c72ba3e9941f5f_ROI.svg
128 ms
64c18caa6b899757295c8f80_blue%20arrow.svg
133 ms
653ad34926bfa0d28f3af5bb_portfolio.svg
131 ms
653ad3495a66e8e414006e94_space.svg
140 ms
653ad34928a1ff47c169b67a_workplace.svg
142 ms
653ad34965a9716ee31e4877_cleaning.svg
143 ms
653ad3493efce7a205ab79ea_availability.svg
144 ms
651b3c5bb00b93fcdde59594_home_v2_entry%20lr%20feature.png
190 ms
651b3c5b788dca132bb297e3_home_v2_open%20area.png
147 ms
6671eb3a668ba5e4aa802f60_Screenshot%202024-06-18%20at%201.12.31%E2%80%AFPM.png
194 ms
66673662a03421bc3c39aae5_Slide%2016_9%20-%205.png
191 ms
6661f7cec09118da555ad94e_Screenshot%202024-05-29%20at%204.17.43%E2%80%AFPM.png
196 ms
6537ecc9681a2cfb55acdaa7_home_trusted%20customers%20bkg.png
198 ms
65450da81fec4afed1bdd56f_trusted%20customer%20logos.png
172 ms
61f4636c55c90484f87e63dd_Aeonik-Light.ttf
147 ms
61f4636c5d0dd98dd29a2c29_Aeonik-Thin.ttf
207 ms
5f49cfb0cfe39c60b90e9999_Aeonik-Regular.ttf
298 ms
5f49cfb0a5fd5b3412a681bc_Aeonik-Medium.ttf
275 ms
5f49cfb07c2fee5f311b6b66_Aeonik-Bold.ttf
273 ms
6654ab14912b5fe6df4245ad_AeonikFono-Black.woff
250 ms
62acf5d92c2bd4d356af1181_AeonikMono-Regular.woff
226 ms
62ac91fbeebc24788e99d483_AeonikMono-Medium.ttf
296 ms
62ac91fb57b85977aee7be08_AeonikMono-Light.ttf
274 ms
62ac91fb87101a86f5ef0bd5_AeonikMono-Thin.ttf
295 ms
62ac91fbead36995d984300f_AeonikMono-Bold.ttf
317 ms
i
10 ms
i
35 ms
i
34 ms
i
34 ms
i
56 ms
i
56 ms
i
50 ms
i
71 ms
location
124 ms
otBannerSdk.js
40 ms
density.io accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
density.io 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
density.io 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
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 Density.io 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 Density.io 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.
density.io
Open Graph data is detected on the main page of Density. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: