Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

blog.regus.ca

Magazine Canada - powered by Regus

Page Load Speed

2.4 sec in total

First Response

203 ms

Resources Loaded

1.8 sec

Page Rendered

439 ms

blog.regus.ca screenshot

About Website

Click here to check amazing Blog Regus content for Canada. Otherwise, check out these important facts you probably never knew about blog.regus.ca

powered by Regus

Visit blog.regus.ca

Key Findings

We analyzed Blog.regus.ca page load time and found that the first response time was 203 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

blog.regus.ca performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.446

20/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

blog.regus.ca

203 ms

78 ms

style.css

42 ms

subscriptions.css

60 ms

widgets.css

60 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.regus.ca, 39% (50 requests) were made to Regus.ca and 8% (10 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Steppingstonellc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (44%)

Content Size

3.2 MB

After Optimization

1.8 MB

In fact, the total size of Blog.regus.ca main page is 3.2 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. 65% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 92.6 kB

  • Original 108.4 kB
  • After minification 76.7 kB
  • After compression 15.7 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. This page needs HTML code to be minified as it can gain 31.7 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 92.6 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 67.2 kB

  • Original 1.4 MB
  • After minification 1.3 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. Blog Regus images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.2 MB

  • Original 1.6 MB
  • After minification 1.3 MB
  • After compression 434.8 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 1.2 MB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 88.2 kB

  • Original 106.4 kB
  • After minification 82.2 kB
  • After compression 18.2 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. Blog.regus.ca needs all CSS files to be minified and compressed as it can save up to 88.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (49%)

Requests Now

119

After Optimization

61

The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog 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 35 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

blog.regus.ca accessibility score

72

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

blog.regus.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

blog.regus.ca SEO score

98

Search Engine Optimization Advices

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 Blog.regus.ca 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 Blog.regus.ca 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 Blog 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: