Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

exchange200.com

Exchange 200 | New Office and Retail Space | Exchange St Malden, MA

Page Load Speed

3.7 sec in total

First Response

173 ms

Resources Loaded

2.7 sec

Page Rendered

812 ms

About Website

Welcome to exchange200.com homepage info - get ready to check Exchange 200 best content right away, or after learning these important things about exchange200.com

Exchange 200 is a new commercial property featuring rental Office Space, Retail Space, and Data Center space at 200 Exchange St in Malden, Massachusetts

Visit exchange200.com

Key Findings

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

Performance Metrics

exchange200.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value22.8 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

www.exchange200.com

173 ms

js

88 ms

4lb1s.css

30 ms

n2.min.js

96 ms

smartslider-frontend.min.js

138 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Exchange200.com, 14% (8 requests) were made to Use.typekit.net and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (307 ms) belongs to the original domain Exchange200.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.2 kB (4%)

Content Size

3.4 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Exchange200.com main page is 3.4 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. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 119.4 kB

  • Original 146.1 kB
  • After minification 144.3 kB
  • After compression 26.8 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 119.4 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 29.4 kB

  • Original 3.0 MB
  • After minification 2.9 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. Exchange 200 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 600 B

  • Original 244.7 kB
  • After minification 244.7 kB
  • After compression 244.1 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

-2%

Potential reduce by 840 B

  • Original 49.0 kB
  • After minification 49.0 kB
  • After compression 48.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. Exchange200.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (41%)

Requests Now

46

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

exchange200.com accessibility score

88

Accessibility Issues

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.

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

Links do not have a discernible name

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

exchange200.com SEO score

90

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 Exchange200.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 Exchange200.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 Exchange 200. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: