Tools & Wizards About Us
vanwert.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

vanwert.org

City of Van Wert, OH :: Helpful Resources and Information

Page Load Speed

3.3 sec in total

First Response

79 ms

Resources Loaded

2.7 sec

Page Rendered

538 ms

vanwert.org screenshot

About Website

Click here to check amazing Van Wert content. Otherwise, check out these important facts you probably never knew about vanwert.org

The City of Van Wert is a thriving midwest community that is experiencing explosive growth and opportunity for community members.

Visit vanwert.org

Key Findings

We analyzed Vanwert.org page load time and found that the first response time was 79 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 60% of websites can load faster.

Performance Metrics

vanwert.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

vanwert.org

79 ms

vanwert.org

1208 ms

tribe-events-pro-mini-calendar-block.min.css

76 ms

style.min.css

193 ms

dashicons.min.css

169 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 77% of them (68 requests) were addressed to the original Vanwert.org, 18% (16 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Vanwert.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (57%)

Content Size

4.3 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vanwert.org main page is 4.3 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. 65% of websites need less resources to load. CSS take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 139.1 kB

  • Original 170.9 kB
  • After minification 167.4 kB
  • After compression 31.8 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 139.1 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 9.6 kB

  • Original 1.4 MB
  • After minification 1.4 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. Van Wert images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 885.8 kB

  • Original 1.1 MB
  • After minification 790.6 kB
  • After compression 196.7 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 885.8 kB or 82% of the original size.

CSS Optimization

-84%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.5 MB
  • After compression 261.5 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. Vanwert.org needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 84% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vanwert.org

vanwert.org

79 ms

vanwert.org

vanwert.org

1208 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

76 ms

style.min.css

style.min.css

193 ms

dashicons.min.css

dashicons.min.css

169 ms

everest-forms.css

everest-forms.css

196 ms

intlTelInput.css

intlTelInput.css

176 ms

nectar-slider.css

nectar-slider.css

189 ms

style.css

style.css

124 ms

job-listings.css

job-listings.css

170 ms

style.css

style.css

211 ms

font-awesome.min.css

font-awesome.min.css

241 ms

style.css

style.css

385 ms

header-secondary-nav.css

header-secondary-nav.css

236 ms

magnific.css

magnific.css

235 ms

css

css

35 ms

responsive.css

responsive.css

296 ms

style.css

style.css

252 ms

skin-original.css

skin-original.css

272 ms

style.css

style.css

275 ms

js_composer.min.css

js_composer.min.css

346 ms

button-styles.css

button-styles.css

294 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

379 ms

css

css

35 ms

jquery.min.js

jquery.min.js

376 ms

jquery-migrate.min.js

jquery-migrate.min.js

332 ms

js

js

56 ms

variables-skeleton.min.css

variables-skeleton.min.css

311 ms

common-skeleton.min.css

common-skeleton.min.css

374 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

397 ms

variables-full.min.css

variables-full.min.css

402 ms

common-full.min.css

common-full.min.css

409 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

400 ms

css

css

27 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

401 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

392 ms

anime.js

anime.js

436 ms

nectar-slider.js

nectar-slider.js

476 ms

salient-social.js

salient-social.js

443 ms

jquery.easing.js

jquery.easing.js

446 ms

jquery.mousewheel.js

jquery.mousewheel.js

438 ms

priority.js

priority.js

454 ms

transit.js

transit.js

437 ms

waypoints.js

waypoints.js

390 ms

modernizr.js

modernizr.js

345 ms

imagesLoaded.min.js

imagesLoaded.min.js

349 ms

hoverintent.js

hoverintent.js

351 ms

magnific.js

magnific.js

363 ms

superfish.js

superfish.js

363 ms

init.js

init.js

425 ms

touchswipe.min.js

touchswipe.min.js

343 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

324 ms

js_composer_front.min.js

js_composer_front.min.js

336 ms

tribe-common.min.js

tribe-common.min.js

350 ms

query-string.min.js

query-string.min.js

347 ms

underscore-before.js

underscore-before.js

324 ms

underscore.min.js

underscore.min.js

324 ms

dashicons.min.css

dashicons.min.css

333 ms

font-awesome.min.css

font-awesome.min.css

335 ms

underscore-after.js

underscore-after.js

299 ms

manager.min.js

manager.min.js

371 ms

breakpoints.min.js

breakpoints.min.js

361 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

61 ms

grid.png

grid.png

60 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

164 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

164 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

166 ms

icomoon.woff

icomoon.woff

164 ms

Footer-Background.png

Footer-Background.png

151 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

201 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

281 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

454 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

454 ms

City-of-Van-Wert.png

City-of-Van-Wert.png

207 ms

Van-Wert-City-Building.jpg

Van-Wert-City-Building.jpg

178 ms

Park-Department.jpg

Park-Department.jpg

229 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

131 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

176 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

176 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

177 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

179 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

177 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

180 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

179 ms

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

178 ms

KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff

KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff

179 ms

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

177 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff

KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff

180 ms

Accessibility Review

vanwert.org accessibility score

83

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

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

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

vanwert.org SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

vanwert.org

Open Graph data is detected on the main page of Van Wert. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: