Tools & Wizards About Us

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

armstrongfield.com

Salem and North Shore Massachusetts - Armstrong Field Real Estate

Page Load Speed

3.1 sec in total

First Response

155 ms

Resources Loaded

1.5 sec

Page Rendered

1.4 sec

About Website

Visit armstrongfield.com now to see the best up-to-date Armstrong Field content and also check out these interesting facts you probably never knew about armstrongfield.com

Search for Massachusetts homes, condos, lofts and real estate for sale in the MLS including Salem, Boston and all of Essex, Middlesex, and Suffolk Counties. See all photos, video & virtual tours, and ...

Visit armstrongfield.com

Key Findings

We analyzed Armstrongfield.com page load time and found that the first response time was 155 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

armstrongfield.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

armstrongfield.com

155 ms

armstrongfield.com

555 ms

main-689e6d64.css

77 ms

template1.css

76 ms

styleAndTheme.css

71 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Armstrongfield.com, 38% (24 requests) were made to Static.chimeroi.com and 29% (18 requests) were made to Cdn.chime.me. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Cdn.chime.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.8 kB (10%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-82%

Potential reduce by 101.1 kB

  • Original 124.0 kB
  • After minification 116.9 kB
  • After compression 22.9 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 101.1 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 10.3 kB

  • Original 980.6 kB
  • After minification 970.3 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. Armstrong Field images are well optimized though.

CSS Optimization

-3%

Potential reduce by 1.3 kB

  • Original 44.6 kB
  • After minification 44.6 kB
  • After compression 43.3 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. Armstrongfield.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

59

After Optimization

40

  • Images
  • CSS

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

Network Requests Diagram

Accessibility Review

armstrongfield.com accessibility score

62

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

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

armstrongfield.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

armstrongfield.com SEO score

92

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

Image elements do not have [alt] attributes

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