Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

regus.com

Regus | Serviced Office Space, Coworking & Virtual Offices

Page Load Speed

3 sec in total

First Response

170 ms

Resources Loaded

2.2 sec

Page Rendered

641 ms

About Website

Click here to check amazing Regus content for United States. Otherwise, check out these important facts you probably never knew about regus.com

Choose from our extensive global network of office space, coworking, virtual office locations and meeting rooms around the world. Get a quote today.

Visit regus.com

Key Findings

We analyzed Regus.com page load time and found that the first response time was 170 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

regus.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

www.regus.com

170 ms

en-us

1413 ms

ebe309104e273a4a.css

19 ms

polyfills-c67a75d1b6f99dc8.js

36 ms

9064.60a6e4d5ef294d71.js

30 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 99% of them (90 requests) were addressed to the original Regus.com, 1% (1 request) were made to Assets.iwgplc.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Regus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 629.7 kB (82%)

Content Size

765.6 kB

After Optimization

135.9 kB

In fact, the total size of Regus.com main page is 765.6 kB. 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. HTML takes 731.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 629.7 kB

  • Original 731.2 kB
  • After minification 731.0 kB
  • After compression 101.5 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 629.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 14.2 kB
  • After minification 14.2 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. Regus images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 21 B

  • Original 20.2 kB
  • After minification 20.2 kB
  • After compression 20.2 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 57 (65%)

Requests Now

88

After Optimization

31

The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

regus.com accessibility score

100

Accessibility Issues

Best Practices

regus.com best practices score

75

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

regus.com SEO score

91

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regus.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 Regus.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 description is not detected on the main page of Regus. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: