Tools & Wizards About Us
fieldhouse219.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fieldhouse219.com

Domain Name Check & Register, Free Trusted SSL Certificates for Site & Hosting

Page Load Speed

666 ms in total

First Response

67 ms

Resources Loaded

514 ms

Page Rendered

85 ms

fieldhouse219.com screenshot

About Website

Welcome to fieldhouse219.com homepage info - get ready to check Fieldhouse 219 best content right away, or after learning these important things about fieldhouse219.com

Check & register best and cheap domain names for you, your business or organization. Generate and get trusted ssl certificates for web servers, sites, hosting, server on linux, windows, nginx, apache

Visit fieldhouse219.com

Key Findings

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

Performance Metrics

fieldhouse219.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

www.fieldhouse219.com

67 ms

minified.js

43 ms

focus-within-polyfill.js

80 ms

polyfill.min.js

41 ms

thunderbolt-commons.587aa77c.bundle.min.js

129 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fieldhouse219.com, 49% (17 requests) were made to Static.parastorage.com and 34% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (273 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 329.9 kB (51%)

Content Size

652.5 kB

After Optimization

322.6 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-77%

Potential reduce by 327.1 kB

  • Original 422.7 kB
  • After minification 421.1 kB
  • After compression 95.7 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 327.1 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 192 B

  • Original 6.2 kB
  • After minification 6.0 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. Fieldhouse 219 images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 223.6 kB
  • After minification 223.6 kB
  • After compression 220.9 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.

Requests Breakdown

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

Requests Now

17

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fieldhouse 219. 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

www.fieldhouse219.com

www.fieldhouse219.com

67 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

80 ms

polyfill.min.js

polyfill.min.js

41 ms

thunderbolt-commons.587aa77c.bundle.min.js

thunderbolt-commons.587aa77c.bundle.min.js

129 ms

main.317a27be.bundle.min.js

main.317a27be.bundle.min.js

130 ms

lodash.min.js

lodash.min.js

130 ms

react.production.min.js

react.production.min.js

112 ms

react-dom.production.min.js

react-dom.production.min.js

115 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

127 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

129 ms

cb8106_5e4e83a79e5646c9a0ad634e3162de51~mv2_d_2329_3500_s_2.jpg

cb8106_5e4e83a79e5646c9a0ad634e3162de51~mv2_d_2329_3500_s_2.jpg

273 ms

bundle.min.js

bundle.min.js

50 ms

OO_teal_large.png

OO_teal_large.png

201 ms

121 ms

119 ms

110 ms

110 ms

109 ms

104 ms

156 ms

152 ms

156 ms

151 ms

154 ms

147 ms

GwZ_PiN1Aind9Eyjp868Ez8E0i7KZn-EPnyo3HZu7kw.woff

GwZ_PiN1Aind9Eyjp868Ez8E0i7KZn-EPnyo3HZu7kw.woff

8 ms

PyqsDANUgLi2UsdO-d4iZQ.woff

PyqsDANUgLi2UsdO-d4iZQ.woff

4 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

24 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

17 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

8 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

3 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

6 ms

Accessibility Review

fieldhouse219.com accessibility score

92

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

Best Practices

fieldhouse219.com best practices score

92

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

Page has valid source maps

SEO Factors

fieldhouse219.com SEO score

90

Search Engine Optimization Advices

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

fieldhouse219.com

Open Graph description is not detected on the main page of Fieldhouse 219. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: