Tools & Wizards About Us
sandspringsfire.org screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

sandspringsfire.org

Sand Springs Fire Department | Sand Springs, OK - Official Website

Page Load Speed

2 sec in total

First Response

130 ms

Resources Loaded

1.7 sec

Page Rendered

176 ms

sandspringsfire.org screenshot

About Website

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

Explore the Sand Springs Fire Department and learn about the history, the organization, view photos, and more.

Visit sandspringsfire.org

Key Findings

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

sandspringsfire.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.376

28/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

sandspringsfire.org

130 ms

Index.aspx

117 ms

Fire

258 ms

gtm.js

73 ms

gtm.js

148 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Sandspringsfire.org, 76% (26 requests) were made to Sandspringsok.org and 12% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (887 ms) relates to the external source Sandspringsok.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.5 kB (8%)

Content Size

983.6 kB

After Optimization

903.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sandspringsfire.org main page is 983.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 780.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.6 kB

  • Original 66.0 kB
  • After minification 62.9 kB
  • After compression 15.4 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 50.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 780.5 kB
  • After minification 780.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. Sand Springs Fire images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 26.5 kB

  • Original 128.0 kB
  • After minification 128.0 kB
  • After compression 101.5 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 26.5 kB or 21% of the original size.

CSS Optimization

-37%

Potential reduce by 3.3 kB

  • Original 9.0 kB
  • After minification 9.0 kB
  • After compression 5.7 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. Sandspringsfire.org needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (58%)

Requests Now

31

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sandspringsfire.org

sandspringsfire.org

130 ms

Index.aspx

Index.aspx

117 ms

Fire

Fire

258 ms

gtm.js

gtm.js

73 ms

gtm.js

gtm.js

148 ms

antiforgery

antiforgery

94 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

223 ms

jQuery-migrate-1.4.1.js

jQuery-migrate-1.4.1.js

105 ms

1357825072.css

1357825072.css

181 ms

-360199271.css

-360199271.css

180 ms

248816995.js

248816995.js

320 ms

745732998.css

745732998.css

121 ms

APIClient.js

APIClient.js

162 ms

moment.min.js

moment.min.js

177 ms

SplashModalRender.js

SplashModalRender.js

193 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

217 ms

Search.js

Search.js

257 ms

jquery-ui.css

jquery-ui.css

258 ms

ai.0.js

ai.0.js

24 ms

1661096276.js

1661096276.js

328 ms

analytics.js

analytics.js

23 ms

collect

collect

25 ms

js

js

97 ms

js

js

116 ms

Document

Document

57 ms

Document

Document

59 ms

Document

Document

887 ms

Document

Document

60 ms

Document

Document

57 ms

Document

Document

128 ms

Document

Document

91 ms

Document

Document

93 ms

Document

Document

94 ms

Print.css

Print.css

48 ms

Accessibility Review

sandspringsfire.org accessibility score

91

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

sandspringsfire.org best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

sandspringsfire.org SEO score

92

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

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

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

sandspringsfire.org

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