Tools & Wizards About Us
220elm.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

220elm.com

220 Elm | Inspired - A High Point Market Showroom Facility

Page Load Speed

724 ms in total

First Response

55 ms

Resources Loaded

390 ms

Page Rendered

279 ms

220elm.com screenshot

About Website

Click here to check amazing 220 Elm content. Otherwise, check out these important facts you probably never knew about 220elm.com

A High Point Market showroom facility, 220 Elm is home to 50 exhibitors and a favorite destination for Top 100 furniture retailers.

Visit 220elm.com

Key Findings

We analyzed 220elm.com page load time and found that the first response time was 55 ms and then it took 669 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

220elm.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

220elm.com

55 ms

style.css

16 ms

modernizr.min.js

23 ms

jquery.min.js

12 ms

script.min.js

104 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 76% of them (19 requests) were addressed to the original 220elm.com, 8% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (239 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.1 kB (5%)

Content Size

665.7 kB

After Optimization

629.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 220elm.com main page is 665.7 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. 25% of websites need less resources to load. Images take 544.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 19.6 kB

  • Original 24.8 kB
  • After minification 22.4 kB
  • After compression 5.2 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 19.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.0 kB

  • Original 544.4 kB
  • After minification 543.4 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. 220 Elm images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 4.3 kB

  • Original 73.4 kB
  • After minification 73.4 kB
  • After compression 69.0 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.

CSS Optimization

-48%

Potential reduce by 11.1 kB

  • Original 23.1 kB
  • After minification 23.1 kB
  • After compression 12.1 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. 220elm.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (28%)

Requests Now

18

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

220elm.com

220elm.com

55 ms

style.css

style.css

16 ms

modernizr.min.js

modernizr.min.js

23 ms

jquery.min.js

jquery.min.js

12 ms

script.min.js

script.min.js

104 ms

analytics.js

analytics.js

24 ms

embed

embed

239 ms

logo.png

logo.png

63 ms

intro.jpg

intro.jpg

80 ms

block-cta-events.jpg

block-cta-events.jpg

72 ms

link-arrow.png

link-arrow.png

73 ms

block-cta-building.jpg

block-cta-building.jpg

74 ms

block-cta-leasing.jpg

block-cta-leasing.jpg

73 ms

block-cta-exhibitors.jpg

block-cta-exhibitors.jpg

98 ms

share.png

share.png

93 ms

logo-inverted.png

logo-inverted.png

85 ms

collect

collect

16 ms

2F3BE6_1_0.woff

2F3BE6_1_0.woff

17 ms

2F3BE6_2_0.woff

2F3BE6_2_0.woff

21 ms

2F3BE6_0_0.woff

2F3BE6_0_0.woff

25 ms

js

js

65 ms

2F3BE6_1_0.ttf

2F3BE6_1_0.ttf

9 ms

2F3BE6_2_0.ttf

2F3BE6_2_0.ttf

12 ms

2F3BE6_0_0.ttf

2F3BE6_0_0.ttf

12 ms

js

js

43 ms

Accessibility Review

220elm.com accessibility score

69

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

<frame> or <iframe> elements do not have a title

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

220elm.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

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

220elm.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

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 220elm.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 220elm.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

220elm.com

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