Tools & Wizards About Us
explorefountainpark.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

explorefountainpark.com

Wilbraham's Fountain Park – Fountain Park is a 144 acre forest preserve on Tinkham Road in Wilbraham

Page Load Speed

7.8 sec in total

First Response

2.8 sec

Resources Loaded

4.6 sec

Page Rendered

317 ms

explorefountainpark.com screenshot

About Website

Click here to check amazing Explore Fountain Park content. Otherwise, check out these important facts you probably never knew about explorefountainpark.com

Visit explorefountainpark.com

Key Findings

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

Performance Metrics

explorefountainpark.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

explorefountainpark.com

2823 ms

style.min.css

58 ms

wc-blocks-vendors-style.css

111 ms

wc-blocks-style.css

176 ms

styles.css

160 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 83% of them (62 requests) were addressed to the original Explorefountainpark.com, 11% (8 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Explorefountainpark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.3 kB (6%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 75.1 kB

  • Original 96.1 kB
  • After minification 95.4 kB
  • After compression 21.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 75.1 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 3.1 kB

  • Original 631.4 kB
  • After minification 628.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. Explore Fountain Park images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.9 kB

  • Original 465.4 kB
  • After minification 465.4 kB
  • After compression 462.5 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.

CSS Optimization

-5%

Potential reduce by 10.2 kB

  • Original 219.4 kB
  • After minification 219.4 kB
  • After compression 209.1 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. Explorefountainpark.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 56 (85%)

Requests Now

66

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

explorefountainpark.com

explorefountainpark.com

2823 ms

style.min.css

style.min.css

58 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

111 ms

wc-blocks-style.css

wc-blocks-style.css

176 ms

styles.css

styles.css

160 ms

tp_twitter_plugin.css

tp_twitter_plugin.css

159 ms

woocommerce-layout.css

woocommerce-layout.css

160 ms

woocommerce.css

woocommerce.css

162 ms

give.css

give.css

167 ms

give-donation-summary.css

give-donation-summary.css

211 ms

pagenavi-css.css

pagenavi-css.css

212 ms

css

css

38 ms

css

css

41 ms

css

css

39 ms

font-awesome.min.css

font-awesome.min.css

212 ms

owl.carousel.min.css

owl.carousel.min.css

215 ms

animate.css

animate.css

217 ms

flipclock.css

flipclock.css

222 ms

slimmenu.min.css

slimmenu.min.css

263 ms

progressbar.css

progressbar.css

261 ms

bootstrap.min.css

bootstrap.min.css

269 ms

styles.css

styles.css

475 ms

colors.css

colors.css

268 ms

responsive.css

responsive.css

282 ms

css

css

39 ms

js_composer.min.css

js_composer.min.css

348 ms

jquery.min.js

jquery.min.js

318 ms

jquery-migrate.min.js

jquery-migrate.min.js

320 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

321 ms

add-to-cart.min.js

add-to-cart.min.js

321 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

371 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

372 ms

wp-polyfill.min.js

wp-polyfill.min.js

379 ms

hooks.min.js

hooks.min.js

373 ms

i18n.min.js

i18n.min.js

399 ms

give.js

give.js

432 ms

wc-quantity-increment.min.js

wc-quantity-increment.min.js

424 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

426 ms

number-polyfill.min.js

number-polyfill.min.js

433 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

451 ms

css

css

31 ms

style.css

style.css

586 ms

rs6.css

rs6.css

536 ms

respond.min.js

respond.min.js

490 ms

flexibility.js

flexibility.js

442 ms

index.js

index.js

451 ms

index.js

index.js

449 ms

rbtools.min.js

rbtools.min.js

522 ms

rs6.min.js

rs6.min.js

614 ms

js.cookie.min.js

js.cookie.min.js

428 ms

woocommerce.min.js

woocommerce.min.js

399 ms

cart-fragments.min.js

cart-fragments.min.js

400 ms

give-donation-summary.js

give-donation-summary.js

396 ms

bootstrap.min.js

bootstrap.min.js

409 ms

plugins.js

plugins.js

465 ms

scripts.js

scripts.js

405 ms

jquery.validate.min.js

jquery.validate.min.js

395 ms

js_composer_front.min.js

js_composer_front.min.js

515 ms

logo-1.png

logo-1.png

173 ms

dummy.png

dummy.png

190 ms

FP-Sponsors-11-1-679x1120.jpg

FP-Sponsors-11-1-679x1120.jpg

357 ms

FP-Sponsors-07-1-680x1120.jpg

FP-Sponsors-07-1-680x1120.jpg

271 ms

FP-Sponsors-02-679x1120.jpg

FP-Sponsors-02-679x1120.jpg

335 ms

FP-Sponsors-06-1-680x1120.jpg

FP-Sponsors-06-1-680x1120.jpg

341 ms

foo-wiget-map.png

foo-wiget-map.png

230 ms

tDbD2oWUg0MKqScQ6A.ttf

tDbD2oWUg0MKqScQ6A.ttf

56 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

148 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

164 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

166 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

166 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf

164 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf

164 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf

165 ms

explorefountainpark.com

explorefountainpark.com

493 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

55 ms

Accessibility Review

explorefountainpark.com accessibility score

70

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.

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

Links do not have a discernible name

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

explorefountainpark.com best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

explorefountainpark.com SEO score

93

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

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

explorefountainpark.com

Open Graph description is not detected on the main page of Explore Fountain Park. 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: