2 sec in total
199 ms
1.1 sec
770 ms
Click here to check amazing Common content for United States. Otherwise, check out these important facts you probably never knew about common.com
Common offers private furnished bedrooms in beautiful shared suites. Enjoy competitive rates, all-inclusive options, a built-in community, and more.
Visit common.comWe analyzed Common.com page load time and found that the first response time was 199 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
common.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value21.1 s
0/100
25%
Value25.8 s
0/100
10%
Value35,000 ms
0/100
30%
Value0.079
94/100
15%
Value45.3 s
0/100
10%
199 ms
60 ms
142 ms
406 ms
69 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 72% of them (39 requests) were addressed to the original Common.com, 7% (4 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (406 ms) relates to the external source Ca-eu.cookie-script.com.
Page size can be reduced by 877.6 kB (81%)
1.1 MB
204.9 kB
In fact, the total size of Common.com main page is 1.1 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. 80% 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. HTML takes 1.0 MB which makes up the majority of the site volume.
Potential reduce by 877.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 877.4 kB or 84% of the original size.
Potential reduce by 147 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.
Number of requests can be reduced by 40 (83%)
48
8
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Common. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.common.com
199 ms
js
60 ms
js
142 ms
6fc8495a6cfcaa25a32043a328f8153e.js
406 ms
tachyons.min.css
69 ms
tachyons-flexbox.min.css
80 ms
polyfills-e80e2fcb21b7c88db401.js
56 ms
main-3ea1d10b264a4024c390.js
23 ms
webpack-6e8602f742f9bbfbda74.js
20 ms
framework.6999b91cd438b3364786.js
58 ms
commons.dbcd82843624fa433d67.js
18 ms
60f19476a605fcb492ebe145aa764829f488873f.8e0a9f00fd21d297d366.js
56 ms
07e6d6e9cff5e8b330b031775d7e6967cd3ed94e.2715c3f707fc31fab198.js
57 ms
394d3dc9dd44adf7cd8e7e8fd1cbdd21a391a355.9650b08be7626d3eb890.js
93 ms
2c346166d71408da96ef83ba03c983c99665131c.1ac9316f977c65d3edce.js
111 ms
4fac54d30deea809752d538140c14a5bb751e209.26aba62ab3858c8b6cfb.js
97 ms
1e6a328f511a7be084420a0cd52adcc9641146b2.eec927403ee4fc8c9ef8.js
94 ms
_app-72d74a96f8f134a1a4fc.js
99 ms
75fc9c18.d0dae9d289431d419000.js
95 ms
6c797e68d15af6c37cd474cfce16983e28c25039.3fddb04f61420cb043dc.js
101 ms
dcb1b142c240868be71cfe5e5eeb4698fe947fbb.dc66bfccbd08f14c34c9.js
103 ms
41cbe1caecbc04b0b57469e03c4b3415f2079b91.60cb06e898d2933f353a.js
98 ms
436193fcdc46b874873406ce8ef09d992d057235.a739c9aff722aa44942b.js
97 ms
ed5bfe53b5bb3cc43144b23fb38408fde390d935.67c95292484b72877565.js
103 ms
f2a0bd894aabd45f5e25cacaa59f7d1d22b2ec90.ee292db30e0103347c69.js
104 ms
84afd3ba861b78d1ee8fdd5020b73ae8180797d2.446e2816b6d3d89d5ea8.js
104 ms
index-0273c8c05603b6dde131.js
345 ms
_buildManifest.js
106 ms
_ssgManifest.js
105 ms
conversion_async.js
125 ms
js
112 ms
js
181 ms
92 ms
common-logo-white.svg
10 ms
common-logo.svg
12 ms
common-mark-white.svg
11 ms
common-mark-black-mobile.svg
5 ms
s-fb.svg
7 ms
s-tw.svg
15 ms
s-ig.svg
17 ms
s-p.svg
15 ms
969ff9c1833a881d55fa.css
8 ms
127 ms
a729aa6db75750eff1f3.css
67 ms
analytics.js
7 ms
collect
129 ms
breadcrumbs-arrow.svg
69 ms
collect
225 ms
blinkloader.min.js
276 ms
apercu_regular_pro.woff
192 ms
apercu_medium_pro.woff
193 ms
apercu_bold_pro.woff
215 ms
TiemposHeadlineWeb-Semibold.woff
190 ms
ga-audiences
60 ms
common.com 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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.
common.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
common.com 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 Common.com 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 Common.com 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.
common.com
Open Graph data is detected on the main page of Common. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: