Tools & Wizards About Us
stpaulfire.org screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 95% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

stpaulfire.org

St. Paul Fire District | Fire and Rescue Agency in St. Paul, Oregon

Page Load Speed

5.6 sec in total

First Response

193 ms

Resources Loaded

2.1 sec

Page Rendered

3.3 sec

stpaulfire.org screenshot

About Website

Visit stpaulfire.org now to see the best up-to-date St Paul Fire content and also check out these interesting facts you probably never knew about stpaulfire.org

St. Paul Fire District provides fire suppression and emergency medical services to the residents of St. Paul, Oregon.

Visit stpaulfire.org

Key Findings

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

Performance Metrics

stpaulfire.org performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

stpaulfire.org

193 ms

stpaulfire.org

343 ms

style.min.css

346 ms

ae-pro.min.css

379 ms

style.css

127 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 81% of them (70 requests) were addressed to the original Stpaulfire.org, 16% (14 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Stpaulfire.org.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images

In fact, the total size of Stpaulfire.org main page is 2.2 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 122.5 kB

  • Original 145.2 kB
  • After minification 139.8 kB
  • After compression 22.7 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 122.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 3.9 kB

  • Original 2.0 MB
  • After minification 2.0 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. St Paul Fire images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 53 (80%)

Requests Now

66

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St Paul 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 27 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stpaulfire.org

stpaulfire.org

193 ms

stpaulfire.org

stpaulfire.org

343 ms

style.min.css

style.min.css

346 ms

ae-pro.min.css

ae-pro.min.css

379 ms

style.css

style.css

127 ms

cff-style.min.css

cff-style.min.css

158 ms

vegas.min.css

vegas.min.css

101 ms

unsemantic-grid.min.css

unsemantic-grid.min.css

180 ms

style.min.css

style.min.css

180 ms

mobile.min.css

mobile.min.css

189 ms

font-icons.min.css

font-icons.min.css

206 ms

elementor-icons.min.css

elementor-icons.min.css

209 ms

frontend-legacy.min.css

frontend-legacy.min.css

202 ms

frontend.min.css

frontend.min.css

321 ms

post-3853.css

post-3853.css

230 ms

frontend.min.css

frontend.min.css

238 ms

all.min.css

all.min.css

392 ms

v4-shims.min.css

v4-shims.min.css

351 ms

post-54.css

post-54.css

346 ms

post-4181.css

post-4181.css

344 ms

post-15.css

post-15.css

415 ms

post-31.css

post-31.css

353 ms

widget.css

widget.css

400 ms

fontawesome.min.css

fontawesome.min.css

345 ms

solid.min.css

solid.min.css

351 ms

regular.min.css

regular.min.css

351 ms

brands.min.css

brands.min.css

366 ms

style-front-end.css

style-front-end.css

362 ms

css

css

213 ms

animations.min.css

animations.min.css

414 ms

ae-pro.min.js

ae-pro.min.js

327 ms

index.min.js

index.min.js

327 ms

ae-editor.min.js

ae-editor.min.js

756 ms

scripts.js

scripts.js

313 ms

element.js

element.js

288 ms

cff-scripts.js

cff-scripts.js

315 ms

vegas.min.js

vegas.min.js

315 ms

back-to-top.min.js

back-to-top.min.js

316 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

317 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

308 ms

webpack.runtime.min.js

webpack.runtime.min.js

311 ms

frontend-modules.min.js

frontend-modules.min.js

243 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

655 ms

wp-polyfill.min.js

wp-polyfill.min.js

248 ms

hooks.min.js

hooks.min.js

650 ms

i18n.min.js

i18n.min.js

666 ms

frontend.min.js

frontend.min.js

624 ms

waypoints.min.js

waypoints.min.js

648 ms

core.min.js

core.min.js

656 ms

swiper.min.js

swiper.min.js

594 ms

share-link.min.js

share-link.min.js

523 ms

dialog.min.js

dialog.min.js

511 ms

frontend.min.js

frontend.min.js

577 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

506 ms

preloaded-modules.min.js

preloaded-modules.min.js

503 ms

jquery.sticky.min.js

jquery.sticky.min.js

562 ms

lazyload.min.js

lazyload.min.js

512 ms

engine-background.jpg

engine-background.jpg

567 ms

firefighter_floating.png

firefighter_floating.png

295 ms

medic-background.jpg

medic-background.jpg

1045 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

83 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

170 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

168 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

179 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

264 ms

fa-solid-900.woff

fa-solid-900.woff

484 ms

fa-regular-400.woff

fa-regular-400.woff

444 ms

fa-brands-400.woff

fa-brands-400.woff

446 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

221 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

224 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

223 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

221 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

221 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

260 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

251 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

259 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

234 ms

generatepress.woff

generatepress.woff

262 ms

st-paul-fire-logo-300x236.png

st-paul-fire-logo-300x236.png

413 ms

asmith.jpg

asmith.jpg

413 ms

spf-mem-badge.png

spf-mem-badge.png

674 ms

firemed-logo-sm.png

firemed-logo-sm.png

675 ms

who-we-are-st-paul.jpg

who-we-are-st-paul.jpg

676 ms

fire-station_750.jpg

fire-station_750.jpg

693 ms

st-paul-fire-btl-1-1024x768.jpg

st-paul-fire-btl-1-1024x768.jpg

696 ms

st-paul-fire-logo.png

st-paul-fire-logo.png

695 ms

Accessibility Review

stpaulfire.org accessibility score

98

Accessibility Issues

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

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

SEO Factors

stpaulfire.org SEO score

98

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

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

stpaulfire.org

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