5.8 sec in total
974 ms
4.3 sec
508 ms
Click here to check amazing We Work Labs content for India. Otherwise, check out these important facts you probably never knew about weworklabs.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 weworklabs.comWe analyzed Weworklabs.com page load time and found that the first response time was 974 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
weworklabs.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value8.7 s
1/100
25%
Value3.3 s
90/100
10%
Value730 ms
41/100
30%
Value0.028
100/100
15%
Value8.7 s
36/100
10%
974 ms
50 ms
65 ms
184 ms
28 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Weworklabs.com, 10% (10 requests) were made to Wework-com.imgix.net and 7% (7 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (974 ms) relates to the external source Wework.com.
Page size can be reduced by 1.3 MB (32%)
4.0 MB
2.7 MB
In fact, the total size of Weworklabs.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. 70% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 141.1 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 141.1 kB or 85% 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 Labs images are well optimized though.
Potential reduce by 687.6 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 687.6 kB or 58% of the original size.
Potential reduce by 381.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. Weworklabs.com needs all CSS files to be minified and compressed as it can save up to 381.5 kB or 86% of the original size.
Number of requests can be reduced by 59 (67%)
88
29
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Work Labs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.wework.com
974 ms
G6VBH-6F46W-742FC-MV5D7-63CSR
50 ms
js_visitor_settings.php
65 ms
live.js
184 ms
config.js
28 ms
vis_opt.js
122 ms
v.gif
3 ms
fonts-fd7b9a46cf7c0624f8a7aa2b73746bb5.css
142 ms
fonts.css
265 ms
icons.css
382 ms
application-f1670c59fb87ba503560ff243390b741.css
144 ms
modernizr-70b4df79231ec09e9e5c0cb1b9c3b837.js
140 ms
base-52ef5499fad9fa3226711af5ec8e7bfb.js
177 ms
isMobile-5bcad163b6cdc138373dc23556faca4f.js
139 ms
we-analytics-e951304615fb8b79ab766b8947abb399.js
140 ms
conversion_async.js
143 ms
js
137 ms
application-7bc348483a0293b52ac313ed0fc7bc3f.js
175 ms
home-ebdb0dad44c3b3d983d08f623050ac8a.js
173 ms
swap.js
137 ms
D57563A697E4485D2.css
8 ms
data
491 ms
analytics.min.js
123 ms
global-s46fee6e9fc-0385a88d5e3688df02e906bcaac8324e.png
15 ms
white_play-ef5e0382b6c64ee5261b48f5cc15b901.png
35 ms
member_icons-seb60e1bb34-da1a14fc68931e87f924a8cef4d10258.png
54 ms
apercu_light-e2a58cb1249c9cf59160d8c7502df66f.woff
43 ms
apercu_regular-1a4bcd8ad3072a5cf348a019c15d79bd.woff
43 ms
apercu_medium-7a7c8927d881e8e32a83f6db0abd28bf.woff
43 ms
apercu_bold-c83ca6bcb8edb45ef8f4de110578d93f.woff
43 ms
4uXeigqVsHfFV03lHXV+bKOAP+dnpRhC30juxVj1LYLFHXcCLfJc11CyggWvt52VrpLlyMFFefwY6jCQ8empzlM7PjwixS+l+zjY
41 ms
l.gif
681 ms
hotjar-10122.js
809 ms
14D_Austin-2.jpg
345 ms
left_arrow_gallery-190444ad18574f2851af7f7837342d79.png
279 ms
img1.png
447 ms
swap_session.js
226 ms
20131211_WeWork_222_Broadway-11.jpg
147 ms
20150409_KIND_Event-36.jpg
127 ms
right_arrow_gallery-b0d7bbbb5598b0588ddda9b0c3a8eb0c.png
66 ms
ajax-loader-ac275f639275f255e9de5cd0c965c3ae.gif
66 ms
image_shadow-a6257c619b137c7225233f23ba8a9aed.png
65 ms
sprite-next2x-629ebc950b221958ab7dd41a0fbe22b1.png
66 ms
1.png
306 ms
post_feed_5.png
177 ms
post_feed_1.png
176 ms
post_feed_2.png
176 ms
post_feed_3.png
176 ms
post_feed_4.png
218 ms
post_bond_st.png
220 ms
post_trinet.png
216 ms
post_indinero.png
274 ms
p
511 ms
loader0.js
217 ms
analytics.js
91 ms
mixpanel-2-latest.min.js
106 ms
gtm.js
126 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
94 ms
linkid.js
10 ms
107 ms
106 ms
collect
28 ms
collect
126 ms
roundtrip.js
91 ms
fbevents.js
130 ms
insight.min.js
112 ms
90 ms
9765-683-10-1116.js
34 ms
91 ms
c
225 ms
187 ms
SARYGEHYGBF2ND5EJLN3A2.js
55 ms
out
11 ms
157 ms
out
6 ms
out
41 ms
out
56 ms
out
57 ms
out
65 ms
39 ms
u.php
143 ms
sync
90 ms
adsct
136 ms
pixel
83 ms
tap.php
10 ms
377928.gif
9 ms
in
13 ms
sd
10 ms
nr-885.min.js
153 ms
pd.js
291 ms
application2.js
139 ms
collect
34 ms
visit-data
217 ms
icap.js
122 ms
9c71fe6a53
132 ms
storage.html
56 ms
analytics
218 ms
43 ms
storage.js
34 ms
l
35 ms
visits
265 ms
jquery.js
67 ms
2185ce9907b473f8f7ea62875f57f35c.css
89 ms
weworklabs.com accessibility score
weworklabs.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
Page has valid source maps
weworklabs.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
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 Weworklabs.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 Weworklabs.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.
weworklabs.com
Open Graph data is detected on the main page of We Work Labs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: