Tools & Wizards About Us
360.steelcase.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

360.steelcase.com

Research + Insights - Steelcase

Page Load Speed

1.8 sec in total

First Response

57 ms

Resources Loaded

1.2 sec

Page Rendered

538 ms

360.steelcase.com screenshot

About Website

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

360 Magazine issues include articles about our insights and research into space design. Read the latest issue and subscribe to stay up to date.

Visit 360.steelcase.com

Key Findings

We analyzed 360.steelcase.com page load time and found that the first response time was 57 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

360.steelcase.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value6,820 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.425

22/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

360.steelcase.com

57 ms

70 ms

0124d03c-d4fd-442d-a293-07bafed3eeaf.js

64 ms

style1.css

36 ms

style2.css

35 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 360.steelcase.com, 52% (34 requests) were made to Dumy1g3ng547g.cloudfront.net and 18% (12 requests) were made to Images.steelcase.com. The less responsive or slowest element that took the longest time to load (540 ms) relates to the external source Images.steelcase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 899.5 kB (61%)

Content Size

1.5 MB

After Optimization

565.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 360.steelcase.com main page is 1.5 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. 60% of websites need less resources to load. CSS take 630.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 125.0 kB

  • Original 156.0 kB
  • After minification 144.4 kB
  • After compression 31.0 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 125.0 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 13.9 kB

  • Original 331.0 kB
  • After minification 317.1 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. 360 Steelcase images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 228.5 kB

  • Original 347.0 kB
  • After minification 339.5 kB
  • After compression 118.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 228.5 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 532.2 kB

  • Original 630.6 kB
  • After minification 570.7 kB
  • After compression 98.4 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. 360.steelcase.com needs all CSS files to be minified and compressed as it can save up to 532.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (42%)

Requests Now

62

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

360.steelcase.com

360.steelcase.com

57 ms

70 ms

0124d03c-d4fd-442d-a293-07bafed3eeaf.js

0124d03c-d4fd-442d-a293-07bafed3eeaf.js

64 ms

style1.css

style1.css

36 ms

style2.css

style2.css

35 ms

jquery.jqplot.min.css

jquery.jqplot.min.css

31 ms

widget-this-week-full.css

widget-this-week-full.css

31 ms

widget-this-week-theme.min.css

widget-this-week-theme.min.css

25 ms

modernizr.min.js

modernizr.min.js

35 ms

jquery.js

jquery.js

47 ms

jquery-migrate.min.js

jquery-migrate.min.js

35 ms

rjqc-full.min.js

rjqc-full.min.js

55 ms

widget-this-week.min.js

widget-this-week.min.js

47 ms

satelliteLib-c837d2a2c155dfad3fce9ba252e26f2192e22093.js

satelliteLib-c837d2a2c155dfad3fce9ba252e26f2192e22093.js

10 ms

respond.min.js

respond.min.js

6 ms

respond.proxy.js

respond.proxy.js

8 ms

scripts.js

scripts.js

368 ms

wp-embed.min.js

wp-embed.min.js

41 ms

mti_cjk.js

mti_cjk.js

315 ms

id

id

173 ms

analytics.js

analytics.js

165 ms

16-0014451.jpg

16-0014451.jpg

229 ms

Steelcase_360_Issue70_Cover.jpg

Steelcase_360_Issue70_Cover.jpg

150 ms

15-0011892.jpg

15-0011892.jpg

209 ms

15-0011891.jpg

15-0011891.jpg

206 ms

15-0006242.jpg

15-0006242.jpg

150 ms

360Magazine-Issue68_14-0001664.jpg

360Magazine-Issue68_14-0001664.jpg

146 ms

360Magazine-Issue67_14-0000611.jpg

360Magazine-Issue67_14-0000611.jpg

236 ms

360Magazine-Issue66_14-0003969.jpg

360Magazine-Issue66_14-0003969.jpg

537 ms

360Magazine-Issue65_14-0003982.jpg

360Magazine-Issue65_14-0003982.jpg

236 ms

360Magazine-Issue64_14-0003979.jpg

360Magazine-Issue64_14-0003979.jpg

540 ms

360Magazine-Issue63_14-0003981.jpg

360Magazine-Issue63_14-0003981.jpg

536 ms

360Magazine-Issue62_14-0003971.jpg

360Magazine-Issue62_14-0003971.jpg

539 ms

logo.svg

logo.svg

124 ms

bg-shadow-left.png

bg-shadow-left.png

126 ms

bg-shadow-right.png

bg-shadow-right.png

127 ms

360-magazine-for-ipad.png

360-magazine-for-ipad.png

128 ms

steelcase.png

steelcase.png

127 ms

steelcase-hover.png

steelcase-hover.png

129 ms

steelcase-education.png

steelcase-education.png

128 ms

steelcase-education-hover.png

steelcase-education-hover.png

127 ms

steelcase-health.png

steelcase-health.png

127 ms

steelcase-health-hover.png

steelcase-health-hover.png

127 ms

turnstone.png

turnstone.png

126 ms

turnstone-hover.png

turnstone-hover.png

127 ms

coalesse.png

coalesse.png

124 ms

coalesse-hover.png

coalesse-hover.png

127 ms

designtex.png

designtex.png

125 ms

designtex-hover.png

designtex-hover.png

125 ms

polyvision.png

polyvision.png

127 ms

polyvision-hover.png

polyvision-hover.png

127 ms

workspring.png

workspring.png

126 ms

workspring-hover.png

workspring-hover.png

125 ms

print.css

print.css

62 ms

steelcase.woff

steelcase.woff

85 ms

id

id

76 ms

collect

collect

336 ms

collect

collect

144 ms

1822507.js

1822507.js

132 ms

api.ipify.org

api.ipify.org

191 ms

satellite-56ccdd3664746d35840021f3.js

satellite-56ccdd3664746d35840021f3.js

12 ms

satellite-54bfeeed6231660015c20300.js

satellite-54bfeeed6231660015c20300.js

10 ms

s-code-contents-a01d09ddf2c39120b764d972245582c4373407c9.js

s-code-contents-a01d09ddf2c39120b764d972245582c4373407c9.js

8 ms

iframe_api

iframe_api

118 ms

quant.js

quant.js

114 ms

s62267837238032

s62267837238032

96 ms

Accessibility Review

360.steelcase.com accessibility score

82

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

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

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

360.steelcase.com best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

360.steelcase.com SEO score

77

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 360.steelcase.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 360.steelcase.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

360.steelcase.com

Open Graph description is not detected on the main page of 360 Steelcase. 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: