Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wework.com

WeWork | Office Space and Workspace Solutions

Page Load Speed

4.6 sec in total

First Response

271 ms

Resources Loaded

3.9 sec

Page Rendered

404 ms

wework.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

wework.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value4,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (32%)

Content Size

4.0 MB

After Optimization

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.

HTML Optimization

-84%

Potential reduce by 128.8 kB

  • Original 153.4 kB
  • After minification 152.9 kB
  • After compression 24.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 128.8 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 72.7 kB

  • Original 2.2 MB
  • After minification 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. We Work images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 722.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 450.7 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.

CSS Optimization

-81%

Potential reduce by 377.5 kB

  • Original 467.8 kB
  • After minification 464.5 kB
  • After compression 90.3 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.

Requests Breakdown

Number of requests can be reduced by 63 (68%)

Requests Now

93

After Optimization

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.

Accessibility Review

wework.com accessibility score

90

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

wework.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wework.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: