Tools & Wizards About Us
antiochfire.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

antiochfire.org

100 Years of Emergency Response | Antioch IL, Antioch Fire Protection District

Page Load Speed

845 ms in total

First Response

255 ms

Resources Loaded

534 ms

Page Rendered

56 ms

antiochfire.org screenshot

About Website

Welcome to antiochfire.org homepage info - get ready to check Antioch Fire best content right away, or after learning these important things about antiochfire.org

For more than a century, the Antioch Fire Department and First Fire Protection District of Antioch have provided Antioch and surrounding areas with first-rate emergency response and fire suppression s...

Visit antiochfire.org

Key Findings

We analyzed Antiochfire.org page load time and found that the first response time was 255 ms and then it took 590 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

antiochfire.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

www.antiochfire.org

255 ms

minified.js

40 ms

focus-within-polyfill.js

39 ms

polyfill.min.js

32 ms

6023.chunk.min.js

136 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Antiochfire.org, 46% (18 requests) were made to Static.parastorage.com and 44% (17 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (255 ms) belongs to the original domain Antiochfire.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (65%)

Content Size

2.1 MB

After Optimization

759.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Antiochfire.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. 55% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 301.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 1.4 MB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 17.4 kB

  • Original 158.8 kB
  • After minification 141.4 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. Obviously, Antioch Fire needs image optimization as it can save up to 17.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 4.3 kB

  • Original 320.2 kB
  • After minification 320.2 kB
  • After compression 315.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 16 (42%)

Requests Now

38

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.antiochfire.org

www.antiochfire.org

255 ms

minified.js

minified.js

40 ms

focus-within-polyfill.js

focus-within-polyfill.js

39 ms

polyfill.min.js

polyfill.min.js

32 ms

6023.chunk.min.js

6023.chunk.min.js

136 ms

5600.chunk.min.js

5600.chunk.min.js

138 ms

1433.chunk.min.js

1433.chunk.min.js

136 ms

8619.chunk.min.js

8619.chunk.min.js

137 ms

form-app-contacts-phone.chunk.min.js

form-app-contacts-phone.chunk.min.js

137 ms

form-app-text-area.chunk.min.js

form-app-text-area.chunk.min.js

136 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

115 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

116 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

115 ms

lodash.min.js

lodash.min.js

159 ms

react.production.min.js

react.production.min.js

117 ms

react-dom.production.min.js

react-dom.production.min.js

116 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

158 ms

Antioch%20Logo.png

Antioch%20Logo.png

121 ms

bundle.min.js

bundle.min.js

101 ms

c85e05_48527df53a964e4cb69ffa0edc1fac0a~mv2.png

c85e05_48527df53a964e4cb69ffa0edc1fac0a~mv2.png

88 ms

337e66_cc101ccd391c47b18b8d06062a5e9b17~mv2.png

337e66_cc101ccd391c47b18b8d06062a5e9b17~mv2.png

85 ms

c85e05_9b61d1f4f98d47e5a7033da855ea4dde~mv2.webp

c85e05_9b61d1f4f98d47e5a7033da855ea4dde~mv2.webp

87 ms

c85e05_9b61d1f4f98d47e5a7033da855ea4dde~mv2.webp

c85e05_9b61d1f4f98d47e5a7033da855ea4dde~mv2.webp

87 ms

Antioch_052124_171_edited.jpg

Antioch_052124_171_edited.jpg

86 ms

Antioch_052124_105_edited.jpg

Antioch_052124_105_edited.jpg

84 ms

Antioch_052124_010_edited.jpg

Antioch_052124_010_edited.jpg

89 ms

Antioch_052124_108_edited.jpg

Antioch_052124_108_edited.jpg

88 ms

Antioch_052124_020_edited.jpg

Antioch_052124_020_edited.jpg

88 ms

c85e05_09abebd9493843858171b1407f1243c5~mv2.png

c85e05_09abebd9493843858171b1407f1243c5~mv2.png

90 ms

Antioch_052124_205_edited.jpg

Antioch_052124_205_edited.jpg

124 ms

Antioch_052124_137_edited.jpg

Antioch_052124_137_edited.jpg

89 ms

c85e05_929fddacacdd4e9da3fe92e8a44afec8~mv2.jpg

c85e05_929fddacacdd4e9da3fe92e8a44afec8~mv2.jpg

123 ms

c85e05_f9c3b4db609c491eae534c01342e65e9~mv2.jpg

c85e05_f9c3b4db609c491eae534c01342e65e9~mv2.jpg

122 ms

Antioch%20Logo.png

Antioch%20Logo.png

123 ms

GROW%20logo%20icon%20-%20Digital%20Marketing%20Agenc.png

GROW%20logo%20icon%20-%20Digital%20Marketing%20Agenc.png

124 ms

deprecation-en.v5.html

deprecation-en.v5.html

7 ms

bolt-performance

bolt-performance

43 ms

deprecation-style.v5.css

deprecation-style.v5.css

24 ms

right-arrow.svg

right-arrow.svg

22 ms

Accessibility Review

antiochfire.org accessibility score

97

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.

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

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

antiochfire.org SEO score

84

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

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

antiochfire.org

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