Tools & Wizards About Us
fountainbuilding.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

fountainbuilding.com

Hardware Store | Fountain Building Supply | Bessemer, AL

Page Load Speed

1.3 sec in total

First Response

22 ms

Resources Loaded

692 ms

Page Rendered

575 ms

fountainbuilding.com screenshot

About Website

Welcome to fountainbuilding.com homepage info - get ready to check Fountain Building best content right away, or after learning these important things about fountainbuilding.com

We provide lumber, hardware, materials and supplies for construction, building, and home improvement. In business since 1949. Pickup and delivery available.

Visit fountainbuilding.com

Key Findings

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

Performance Metrics

fountainbuilding.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

fountainbuilding.com

22 ms

www.fountainbuilding.com

84 ms

www.fountainbuilding.com

184 ms

hic.js

92 ms

fountain-logo-horizontal-279w.png

315 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 32% of them (6 requests) were addressed to the original Fountainbuilding.com, 21% (4 requests) were made to Static-res-cdn.websites.hibu.com and 16% (3 requests) were made to Le-cdn.hibuwebsites.com. The less responsive or slowest element that took the longest time to load (315 ms) relates to the external source Le-cdn.hibuwebsites.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.8 kB (58%)

Content Size

633.7 kB

After Optimization

265.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 307.2 kB

  • Original 391.3 kB
  • After minification 384.5 kB
  • After compression 84.1 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 307.2 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 472 B

  • Original 14.0 kB
  • After minification 13.5 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. Fountain Building images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 61.0 kB

  • Original 228.1 kB
  • After minification 218.7 kB
  • After compression 167.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 61.0 kB or 27% of the original size.

CSS Optimization

-19%

Potential reduce by 60 B

  • Original 311 B
  • After minification 311 B
  • After compression 251 B

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. Fountainbuilding.com needs all CSS files to be minified and compressed as it can save up to 60 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (67%)

Requests Now

15

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fountainbuilding.com

fountainbuilding.com

22 ms

www.fountainbuilding.com

www.fountainbuilding.com

84 ms

www.fountainbuilding.com

www.fountainbuilding.com

184 ms

hic.js

hic.js

92 ms

fountain-logo-horizontal-279w.png

fountain-logo-horizontal-279w.png

315 ms

hibu-runtime.css

hibu-runtime.css

68 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

102 ms

shutterstock_80238202-1920w.jpg

shutterstock_80238202-1920w.jpg

244 ms

vid-splash-play-1920w.png

vid-splash-play-1920w.png

39 ms

d-js-one-runtime-unified-desktop.min.js

d-js-one-runtime-unified-desktop.min.js

102 ms

d-js-jquery-migrate.min.js

d-js-jquery-migrate.min.js

104 ms

gtm.js

gtm.js

230 ms

ybDynamicPhoneInsertion.js

ybDynamicPhoneInsertion.js

110 ms

AppMeasurement.js

AppMeasurement.js

136 ms

hibu-analytics.min.js

hibu-analytics.min.js

225 ms

omn_setting.js

omn_setting.js

140 ms

f.js

f.js

82 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

55 ms

sdk.js

sdk.js

25 ms

Accessibility Review

fountainbuilding.com accessibility score

97

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.

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fountainbuilding.com SEO score

89

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

fountainbuilding.com

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