Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

hffa.com

Huntersville Family Fitness and Aquatics Center - Where Greatness Grows

Page Load Speed

1.5 sec in total

First Response

133 ms

Resources Loaded

847 ms

Page Rendered

490 ms

hffa.com screenshot

About Website

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

Huntersville Family Fitness & Aquatics (HFFA), is an 88,000-square-foot facility that includes full aquatic and fitness components.

Visit hffa.com

Key Findings

We analyzed Hffa.com page load time and found that the first response time was 133 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 30% of websites can load faster.

Performance Metrics

hffa.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

hffa.com

133 ms

www.hffa.com

87 ms

js

109 ms

js

239 ms

wp-emoji-release.min.js

34 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 80% of them (86 requests) were addressed to the original Hffa.com, 14% (15 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (286 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 348.3 kB (16%)

Content Size

2.1 MB

After Optimization

1.8 MB

In fact, the total size of Hffa.com main page is 2.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. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 168.6 kB

  • Original 199.6 kB
  • After minification 197.7 kB
  • After compression 31.0 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 168.6 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 9.3 kB

  • Original 1.1 MB
  • After minification 1.1 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. Hffa images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 93.8 kB

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

CSS Optimization

-24%

Potential reduce by 76.6 kB

  • Original 321.2 kB
  • After minification 317.1 kB
  • After compression 244.6 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. Hffa.com needs all CSS files to be minified and compressed as it can save up to 76.6 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (83%)

Requests Now

86

After Optimization

15

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

Accessibility Review

hffa.com accessibility score

82

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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