Tools & Wizards About Us
fortwayneparks.org screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    64% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 90

    SEO

    Google-friendlier than
    69% of websites

fortwayneparks.org

Home - Fort Wayne Parks and Recreation

Page Load Speed

3.3 sec in total

First Response

89 ms

Resources Loaded

2.7 sec

Page Rendered

431 ms

fortwayneparks.org screenshot

About Website

Click here to check amazing Fort Wayne Parks content for United States. Otherwise, check out these important facts you probably never knew about fortwayneparks.org

fort wayne Parks,Fort Wayne Parks and Recreation,Fort Wayne,IN, City of Fort Wayne Parks

Visit fortwayneparks.org

Key Findings

We analyzed Fortwayneparks.org page load time and found that the first response time was 89 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fortwayneparks.org performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

fortwayneparks.org

89 ms

www.fortwayneparks.org

1240 ms

gantry.css

80 ms

grid-12.css

84 ms

joomla.css

91 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 92% of them (77 requests) were addressed to the original Fortwayneparks.org, 4% (3 requests) were made to Assets.pinterest.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fortwayneparks.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 668.8 kB (38%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fortwayneparks.org main page is 1.8 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. 50% of websites need less resources to load. Images take 977.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 264.5 kB

  • Original 293.6 kB
  • After minification 168.4 kB
  • After compression 29.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. This page needs HTML code to be minified as it can gain 125.1 kB, which is 43% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 264.5 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 33.0 kB

  • Original 977.5 kB
  • After minification 944.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. Fort Wayne Parks images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 194.5 kB

  • Original 288.8 kB
  • After minification 265.5 kB
  • After compression 94.3 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 194.5 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 176.7 kB

  • Original 212.0 kB
  • After minification 186.0 kB
  • After compression 35.4 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. Fortwayneparks.org needs all CSS files to be minified and compressed as it can save up to 176.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (57%)

Requests Now

81

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fortwayneparks.org

fortwayneparks.org

89 ms

www.fortwayneparks.org

www.fortwayneparks.org

1240 ms

gantry.css

gantry.css

80 ms

grid-12.css

grid-12.css

84 ms

joomla.css

joomla.css

91 ms

joomla.css

joomla.css

87 ms

body.css

body.css

88 ms

header-dark.css

header-dark.css

90 ms

accent-blue.css

accent-blue.css

120 ms

footer-dark.css

footer-dark.css

122 ms

typography.css

typography.css

137 ms

extensions.css

extensions.css

146 ms

thirdparty.css

thirdparty.css

138 ms

demo-styles.css

demo-styles.css

134 ms

template.css

template.css

161 ms

template-webkit.css

template-webkit.css

163 ms

fusionmenu.css

fusionmenu.css

176 ms

style.css

style.css

181 ms

mootools.js

mootools.js

220 ms

caption.js

caption.js

177 ms

piclens.js

piclens.js

206 ms

gantry-totop.js

gantry-totop.js

204 ms

gantry-inputs.js

gantry-inputs.js

218 ms

gantry-module-scroller.js

gantry-module-scroller.js

235 ms

fusion.js

fusion.js

239 ms

shajax.js

shajax.js

245 ms

template.js

template.js

252 ms

style.css

style.css

262 ms

mootools-fpss-comp.js

mootools-fpss-comp.js

263 ms

pinit.js

pinit.js

8 ms

jquery.js

jquery.js

319 ms

template_css.php

template_css.php

50 ms

addsign.gif

addsign.gif

48 ms

addsign_a.gif

addsign_a.gif

49 ms

ga.js

ga.js

14 ms

pinit_fg_en_rect_red_20.png

pinit_fg_en_rect_red_20.png

13 ms

wxBanner

wxBanner

457 ms

lindenwood.jpg

lindenwood.jpg

181 ms

twitter.png

twitter.png

99 ms

facebook.png

facebook.png

92 ms

youtube.png

youtube.png

99 ms

www.fortwayneparks.org

www.fortwayneparks.org

1123 ms

IMG_0216_slid.jpg

IMG_0216_slid.jpg

201 ms

easter2.jpg

easter2.jpg

252 ms

IMG_0006_slid.jpg

IMG_0006_slid.jpg

175 ms

20150701_1217_001_1.jpg

20150701_1217_001_1.jpg

229 ms

IMG_1489.jpg

IMG_1489.jpg

255 ms

IMG_0216_slid.jpg

IMG_0216_slid.jpg

230 ms

easter2.jpg

easter2.jpg

242 ms

IMG_0006_slid.jpg

IMG_0006_slid.jpg

263 ms

20150701_1217_001_1.jpg

20150701_1217_001_1.jpg

264 ms

IMG_1489.jpg

IMG_1489.jpg

283 ms

fun_times_spring_2016.jpg

fun_times_spring_2016.jpg

339 ms

news_120px.png

news_120px.png

298 ms

2016_series_v3.jpg

2016_series_v3.jpg

347 ms

Kidbro_Icon.jpg

Kidbro_Icon.jpg

307 ms

new_blue_64x64.png

new_blue_64x64.png

326 ms

blank.png

blank.png

339 ms

capra_logo.png

capra_logo.png

350 ms

kaboom_logo_narrow.gif

kaboom_logo_narrow.gif

368 ms

playful_city.jpg

playful_city.jpg

375 ms

BirdTownIndianaLogo.jpg

BirdTownIndianaLogo.jpg

379 ms

header-bg.png

header-bg.png

379 ms

__utm.gif

__utm.gif

56 ms

pill-l.png

pill-l.png

308 ms

pill-r.png

pill-r.png

327 ms

menu-arrows.png

menu-arrows.png

340 ms

search-button.png

search-button.png

337 ms

header-bottom.png

header-bottom.png

351 ms

fontsizer.png

fontsizer.png

352 ms

loading.gif

loading.gif

369 ms

navbar.png

navbar.png

383 ms

next.gif

next.gif

386 ms

prev.gif

prev.gif

392 ms

collect

collect

73 ms

color-gradient.png

color-gradient.png

392 ms

pinit_main.js

pinit_main.js

72 ms

alt_flagsa.png

alt_flagsa.png

364 ms

32a.png

32a.png

383 ms

footer-bg.png

footer-bg.png

347 ms

totop.png

totop.png

353 ms

header1.jpg

header1.jpg

373 ms

header2.jpg

header2.jpg

356 ms

header3.jpg

header3.jpg

374 ms

Accessibility Review

fortwayneparks.org accessibility score

65

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.

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

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

fortwayneparks.org best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fortwayneparks.org 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 Fortwayneparks.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 Fortwayneparks.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

fortwayneparks.org

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