4.6 sec in total
271 ms
3.9 sec
404 ms
Welcome to wework.com homepage info - get ready to check We Work best content for India right away, or after learning these important things about wework.com
Workspace with flexible terms and hybrid solutions, whether your business needs global scale or office space near you. For all the ways you work, we’re here.
Visit wework.comWe analyzed Wework.com page load time and found that the first response time was 271 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wework.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value5.2 s
24/100
25%
Value7.1 s
31/100
10%
Value4,710 ms
0/100
30%
Value0.142
78/100
15%
Value21.1 s
1/100
10%
271 ms
102 ms
80 ms
246 ms
132 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Wework.com, 20% (21 requests) were made to Da6bhbkkgqxyz.cloudfront.net and 9% (10 requests) were made to Wework-com.imgix.net. The less responsive or slowest element that took the longest time to load (990 ms) relates to the external source Static.hotjar.com.
Page size can be reduced by 1.3 MB (32%)
4.0 MB
2.7 MB
In fact, the total size of Wework.com main page is 4.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. 55% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 128.8 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 128.8 kB or 84% of the original size.
Potential reduce by 72.7 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. We Work images are well optimized though.
Potential reduce by 722.3 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 722.3 kB or 62% of the original size.
Potential reduce by 377.5 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. Wework.com needs all CSS files to be minified and compressed as it can save up to 377.5 kB or 81% of the original size.
Number of requests can be reduced by 63 (68%)
93
30
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Work. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.wework.com
271 ms
G6VBH-6F46W-742FC-MV5D7-63CSR
102 ms
js_visitor_settings.php
80 ms
live.js
246 ms
fonts-ad3e94bf4733edae31e5f36f4b25202e.css
132 ms
fonts.css
216 ms
icons.css
395 ms
application-a234f94730a55fe2cf334ad510617974.css
141 ms
modernizr-04a3191e2cababf2034914b9b5c81714.js
128 ms
base-d78e98ecea56f02f36bb1fca16ef9f13.js
141 ms
isMobile-12f6fe009ae6065a37aff603f1b5741b.js
130 ms
we-analytics-0c462daed2def4c7cb8063be576f3404.js
142 ms
conversion_async.js
142 ms
js
152 ms
application-bf30d2b10a0bb1ec7a2f8d488c12d24f.js
147 ms
home-3a5f450d35bfd2863b356a04465fb451.js
140 ms
swap.js
140 ms
9a7f5043d2d2e7dd1438d24bc72e01b7ecbf5075
155 ms
v.gif
41 ms
config.js
32 ms
7F19482C29941782B.css
10 ms
data
274 ms
analytics.min.js
946 ms
global-s46fee6e9fc-e5261500b35b35bfc7ddd035145e6f1c.png
60 ms
white_play-db5218ae6690c289cd96ab1a0042f07f.png
50 ms
member_icons-seb60e1bb34-d698aba51164d07c6704d45c1fb8686e.png
29 ms
apercu_light-eb768096cb66ed613d932769a304bc8b.woff
28 ms
apercu_regular-bf2783d0fd752f5910fcea7c4668250e.woff
28 ms
apercu_medium-21cb63580325ba2ba9840a61aa935c4d.woff
27 ms
apercu_bold-090477aa45e66de88e2cb98997ae277a.woff
27 ms
kV+RV+hKK82Y5KtmXjXzlGYOpZKPzZ7qXqz2O3i3eg9plp3PGC25OBH6vxzy+BEv91ZUqIS9K641lXfU+bGNAh7OT0pxBn0juRdj1TcIFrfcCZ7JPN81lKxgwettZ6WrZDlycFEeP4baD2R8frrz9I73j0rxC02WP2A=
26 ms
hotjar-10122.js
990 ms
14D_Austin-2.jpg
661 ms
left_arrow_gallery-e96d07a04c844571ddd46d25fcfc7e8b.png
461 ms
img1.png
781 ms
show
415 ms
swap_session.js
210 ms
20131211_WeWork_222_Broadway-11.jpg
268 ms
20150409_KIND_Event-36.jpg
321 ms
right_arrow_gallery-44d8f358b14cb71caa1e1a651157aec9.png
146 ms
ajax-loader-535cba876b5f421d59d0f0d7eff7b18c.gif
59 ms
image_shadow-1b617480ddb6f6f92cb31b72f4eea63a.png
59 ms
sprite-next2x-e9b38bb4da069afa12e16607e772ac9d.png
60 ms
1.png
442 ms
post_feed_5.png
207 ms
post_feed_1.png
263 ms
post_feed_2.png
319 ms
post_feed_3.png
256 ms
post_feed_4.png
265 ms
post_bond_st.png
353 ms
post_trinet.png
367 ms
post_indinero.png
453 ms
p
644 ms
loader0.js
423 ms
analytics.js
149 ms
mixpanel-2-latest.min.js
129 ms
gtm.js
148 ms
89 ms
82 ms
js
58 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
108 ms
roundtrip.js
179 ms
fbevents.js
470 ms
insight.min.js
196 ms
linkid.js
77 ms
125 ms
i.js
287 ms
collect
70 ms
collect
108 ms
71 ms
SARYGEHYGBF2ND5EJLN3A2.js
20 ms
9765-683-10-1116.js
185 ms
out
7 ms
tr
226 ms
23 ms
out
4 ms
out
39 ms
tr
237 ms
tr
275 ms
u.php
307 ms
sync
188 ms
adsct
224 ms
39 ms
pixel
202 ms
c
210 ms
107 ms
377928.gif
15 ms
js
64 ms
in
35 ms
icap.js
68 ms
sd
40 ms
img
30 ms
visit-data
223 ms
iframe
64 ms
img
32 ms
img
133 ms
tap.php
369 ms
nr-885.min.js
55 ms
pd.js
188 ms
application2.js
266 ms
9c71fe6a53
133 ms
analytics
242 ms
22 ms
l
25 ms
storage.html
68 ms
storage.js
69 ms
wework.com 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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
wework.com 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
Page has valid source maps
wework.com 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wework.com 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 Wework.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.
wework.com
Open Graph data is detected on the main page of We Work. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: