Tools & Wizards About Us
armstrongfloorwall.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

armstrongfloorwall.com

Flooring Store servicing Silver City, NM | Armstrong Floor & Wall

Page Load Speed

2.6 sec in total

First Response

30 ms

Resources Loaded

1.7 sec

Page Rendered

821 ms

armstrongfloorwall.com screenshot

About Website

Click here to check amazing Armstrong Floor Wall content. Otherwise, check out these important facts you probably never knew about armstrongfloorwall.com

Welcome to Armstrong Floor & Wall. Silver City's biggest and best flooring retailer, selling premium carpet, laminate, tile & luxury vinyl. Contact us today!

Visit armstrongfloorwall.com

Key Findings

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

Performance Metrics

armstrongfloorwall.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

74/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value8,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

armstrongfloorwall.com

30 ms

www.armstrongfloorwall.com

92 ms

linkToMainContent.css

238 ms

249208f795ce4e91.css

24 ms

ec58dc1ec78ecb61.css

29 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 49% of them (18 requests) were addressed to the original Armstrongfloorwall.com, 27% (10 requests) were made to Res.cloudinary.com and 22% (8 requests) were made to Clientassets.web.broadlume.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 758.2 kB (62%)

Content Size

1.2 MB

After Optimization

464.5 kB

  • HTML
  • Images

In fact, the total size of Armstrongfloorwall.com main page is 1.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. 35% of websites need less resources to load. HTML takes 874.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 758.2 kB

  • Original 874.0 kB
  • After minification 863.4 kB
  • After compression 115.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 758.2 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 348.7 kB
  • After minification 348.7 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 Floor Wall images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 15 (43%)

Requests Now

35

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

armstrongfloorwall.com

armstrongfloorwall.com

30 ms

www.armstrongfloorwall.com

www.armstrongfloorwall.com

92 ms

linkToMainContent.css

linkToMainContent.css

238 ms

249208f795ce4e91.css

249208f795ce4e91.css

24 ms

ec58dc1ec78ecb61.css

ec58dc1ec78ecb61.css

29 ms

0e643f44e34c25a3.css

0e643f44e34c25a3.css

24 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

358 ms

jquery.min.js

jquery.min.js

53 ms

363-aae1229c166b80b1.js

363-aae1229c166b80b1.js

34 ms

403.de3f0b95d91e5487.js

403.de3f0b95d91e5487.js

37 ms

webpack-0c3736d6ad52c937.js

webpack-0c3736d6ad52c937.js

40 ms

framework-98e92f1440da59ed.js

framework-98e92f1440da59ed.js

267 ms

main-f21d1c68d3c6c86d.js

main-f21d1c68d3c6c86d.js

49 ms

_app-ba8daacd762b36c8.js

_app-ba8daacd762b36c8.js

52 ms

387-cd8eb5b7ec225a7a.js

387-cd8eb5b7ec225a7a.js

70 ms

102-32d0107d79807b4c.js

102-32d0107d79807b4c.js

409 ms

%5BcontentPage%5D-b18f591d1c24b78e.js

%5BcontentPage%5D-b18f591d1c24b78e.js

63 ms

_buildManifest.js

_buildManifest.js

73 ms

_ssgManifest.js

_ssgManifest.js

189 ms

image.png

image.png

43 ms

_0069_28227_00.jpg

_0069_28227_00.jpg

167 ms

wed03_53_01.jpg

wed03_53_01.jpg

503 ms

cdl81_01_00.jpg

cdl81_01_00.jpg

382 ms

pan_statuario_res_02.jpg

pan_statuario_res_02.jpg

383 ms

r0802_926_00.jpg

r0802_926_00.jpg

1349 ms

adobestock_300645847.jpg

adobestock_300645847.jpg

424 ms

adobestock_296388747.jpg

adobestock_296388747.jpg

406 ms

adobestock_227717698.jpg

adobestock_227717698.jpg

614 ms

adobestock_218771619.jpg

adobestock_218771619.jpg

567 ms

powered-by-ff-light.svg

powered-by-ff-light.svg

450 ms

687831.svg

687831.svg

317 ms

683126.svg

683126.svg

327 ms

683123.svg

683123.svg

323 ms

683124.svg

683124.svg

307 ms

683121.svg

683121.svg

299 ms

683122.svg

683122.svg

333 ms

826417.png

826417.png

619 ms

Accessibility Review

armstrongfloorwall.com accessibility score

78

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

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

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

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

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

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

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

Page has valid source maps

SEO Factors

armstrongfloorwall.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

armstrongfloorwall.com

Open Graph data is detected on the main page of Armstrong Floor Wall. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: