Tools & Wizards About Us
parkboard.org screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

parkboard.org

Springfield-Greene County Park Board | Official Website

Page Load Speed

2.2 sec in total

First Response

94 ms

Resources Loaded

1.6 sec

Page Rendered

452 ms

parkboard.org screenshot

About Website

Click here to check amazing Park Board content for United States. Otherwise, check out these important facts you probably never knew about parkboard.org

Find parks facilities, programs and events in Springfield and Greene County

Visit parkboard.org

Key Findings

We analyzed Parkboard.org page load time and found that the first response time was 94 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

parkboard.org performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.459

19/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

parkboard.org

94 ms

www.parkboard.org

505 ms

gtm.js

55 ms

gtm.js

76 ms

antiforgery

110 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 51% of them (38 requests) were addressed to the original Parkboard.org, 28% (21 requests) were made to Static.xx.fbcdn.net and 9% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (616 ms) belongs to the original domain Parkboard.org.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Parkboard.org 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 115.8 kB

  • Original 142.7 kB
  • After minification 132.5 kB
  • After compression 26.9 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 115.8 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 12.4 kB

  • Original 1.9 MB
  • After minification 1.9 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. Park Board images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 8.9 kB

  • Original 112.8 kB
  • After minification 112.7 kB
  • After compression 103.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.

CSS Optimization

-23%

Potential reduce by 1.8 kB

  • Original 7.9 kB
  • After minification 7.9 kB
  • After compression 6.0 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. Parkboard.org needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 23% of the original size.

Requests Breakdown

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

Requests Now

72

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

parkboard.org

parkboard.org

94 ms

www.parkboard.org

www.parkboard.org

505 ms

gtm.js

gtm.js

55 ms

gtm.js

gtm.js

76 ms

antiforgery

antiforgery

110 ms

gtm.js

gtm.js

108 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

173 ms

jQuery-migrate-1.4.1.js

jQuery-migrate-1.4.1.js

248 ms

-1542169068.css

-1542169068.css

616 ms

506409639.css

506409639.css

326 ms

ai.0.js

ai.0.js

17 ms

248816995.js

248816995.js

335 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

248 ms

Search.js

Search.js

249 ms

jquery-ui.css

jquery-ui.css

252 ms

PausePlay.css

PausePlay.css

323 ms

1700977764.js

1700977764.js

323 ms

Calendar.js

Calendar.js

299 ms

jquery.urlToLink.min.js

jquery.urlToLink.min.js

300 ms

745732998.css

745732998.css

298 ms

APIClient.js

APIClient.js

299 ms

Moment.min.js

Moment.min.js

300 ms

SplashModalRender.js

SplashModalRender.js

369 ms

946409437.js

946409437.js

454 ms

js

js

103 ms

analytics.js

analytics.js

56 ms

js

js

60 ms

collect

collect

87 ms

js

js

84 ms

js

js

89 ms

Rc9i9Ep.png

Rc9i9Ep.png

20 ms

Document

Document

55 ms

Document

Document

51 ms

Document

Document

52 ms

Document

Document

54 ms

Document

Document

378 ms

Document

Document

136 ms

Document

Document

175 ms

Document

Document

136 ms

Document

Document

102 ms

Document

Document

101 ms

Document

Document

140 ms

Path

Path

143 ms

Document

Document

166 ms

like.php

like.php

156 ms

Document

Document

156 ms

Path

Path

146 ms

Document

Document

151 ms

Document

Document

178 ms

page.php

page.php

176 ms

fy_wU0FBvkG.js

fy_wU0FBvkG.js

27 ms

FEppCFCt76d.png

FEppCFCt76d.png

28 ms

lFC1eVji7gN.css

lFC1eVji7gN.css

5 ms

fuU9ChcFal0.css

fuU9ChcFal0.css

7 ms

8zUKAIFBjy-.css

8zUKAIFBjy-.css

9 ms

VWDhCULazb5.js

VWDhCULazb5.js

17 ms

5xOV5e9oy4e.js

5xOV5e9oy4e.js

42 ms

mP12tTiNgO_.js

mP12tTiNgO_.js

42 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

16 ms

owo2sPJxB2z.js

owo2sPJxB2z.js

46 ms

p55HfXW__mM.js

p55HfXW__mM.js

50 ms

k_PjgALRjoR.js

k_PjgALRjoR.js

50 ms

YEtUGb-ToKw.js

YEtUGb-ToKw.js

53 ms

XKFYjgE7mEh.js

XKFYjgE7mEh.js

59 ms

g2XPN2wRGmV.js

g2XPN2wRGmV.js

49 ms

E6qR0C8WEpl.js

E6qR0C8WEpl.js

57 ms

kgAz0TBWoYE.js

kgAz0TBWoYE.js

85 ms

DPxpTcknHiI.js

DPxpTcknHiI.js

84 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

84 ms

288949693_387522356752918_4275053409616563035_n.jpg

288949693_387522356752918_4275053409616563035_n.jpg

40 ms

242718159_218965403608615_4538494620155018651_n.png

242718159_218965403608615_4538494620155018651_n.png

40 ms

u2HYktv2mdq.js

u2HYktv2mdq.js

29 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

23 ms

Print.css

Print.css

48 ms

Accessibility Review

parkboard.org accessibility score

81

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

parkboard.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

parkboard.org SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Parkboard.org 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 Parkboard.org 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

parkboard.org

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