2.2 sec in total
36 ms
731 ms
1.5 sec
Click here to check amazing Roam content for United States. Otherwise, check out these important facts you probably never knew about roam.co
We're starting the first global co-living subscription. Sign a single lease, and you can roam among magical properties across 3 continents.
Visit roam.coWe analyzed Roam.co page load time and found that the first response time was 36 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
roam.co performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value2.2 s
95/100
25%
Value1.6 s
100/100
10%
Value60 ms
100/100
30%
Value0
100/100
15%
Value2.2 s
99/100
10%
36 ms
144 ms
61 ms
84 ms
68 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 58% of them (34 requests) were addressed to the original Roam.co, 22% (13 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to . The less responsive or slowest element that took the longest time to load (368 ms) belongs to the original domain Roam.co.
Page size can be reduced by 176.4 kB (9%)
1.9 MB
1.7 MB
In fact, the total size of Roam.co main page is 1.9 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 14.2 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 14.2 kB or 70% of the original size.
Potential reduce by 19.5 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. Roam images are well optimized though.
Potential reduce by 55.8 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 55.8 kB or 47% of the original size.
Potential reduce by 87.0 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. Roam.co needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 44% of the original size.
Number of requests can be reduced by 9 (22%)
41
32
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
roam.co
36 ms
www.roam.co
144 ms
roam.8b12c20d577c.css
61 ms
normalize.6b411ee09205.css
84 ms
webflow.34b6f7088af2.css
68 ms
roam.webflow.6d0df8e3a0b7.css
81 ms
webfont.js
24 ms
modernizr.a89f4997162b.js
70 ms
roam.05aa02a68209.js
93 ms
css
60 ms
mixpanel-2-latest.min.js
119 ms
fbevents.js
70 ms
icons.5.9a8737b84a21.png
68 ms
bbq.49a6e72d33d2.jpg
197 ms
ROAM_logo_g.64af6f4565da.png
58 ms
roam-room2.1b1bdb637396.jpg
62 ms
community.cb4fa7ded58c.jpg
61 ms
Lima01.1c75da61ca60.jpg
130 ms
DSC04793.4c946d023c31.JPG
189 ms
capoeira.aa25127e0c2b.jpg
186 ms
cooking.11cf1220f2d7.jpg
199 ms
offerings-workshop.e0448234dbc7.png
201 ms
bbq1.20f4b52a01dc.jpg
190 ms
flyte.9655e03f7a7c.jpg
252 ms
talking.d64019204037.jpg
256 ms
calligraphy.2790d90129f6.jpg
254 ms
_MG_3220.1f2bad117eec.jpg
258 ms
tablework.3fcdd775e801.jpg
264 ms
Lima03.fcafb2db254b.jpg
259 ms
chair.92ac1e02a3a4.jpg
300 ms
smilework.4ce90e0d5b0f.jpg
330 ms
roam-bathtub.dbf7840426a0.jpg
327 ms
acroyoga.2b0caf95ffb8.jpg
326 ms
flower.974fded3caa8.jpg
316 ms
hammocks.b64a9dcc757e.jpg
331 ms
social-18.fdf513e96a88.svg
348 ms
social-03.7df6fefeebc8.svg
365 ms
social-08.35e7a9bff936.svg
368 ms
analytics.js
24 ms
hfyUHXUAAA=
6 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
70 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
70 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
100 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
108 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
126 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
118 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
117 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
126 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
126 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
126 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
129 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
129 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
135 ms
3vstc9+Bxx0yGFHwvs45rgTTjrltDPOOue8Cy665LIrrspwzXU33HTLbZnuuOteeGMPPPTIY088lSXbMzmeeyHXS3leeS3fG2+9894HBT765PNvwoVuzwAAAA==
5 ms
AYd5lpw=
5 ms
137 ms
79 ms
77 ms
collect
73 ms
roam.co 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.
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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
roam.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
roam.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roam.co can be misinterpreted by Google and other search engines. Our service has detected that English 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 Roam.co 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.
roam.co
Open Graph data is detected on the main page of Roam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: