Tools & Wizards About Us
flatsafe.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

flatsafe.com

FlatSafe Oklahoma Tornado Storm Shelters | OKC & Tulsa | Underground & Above Safe Rooms

Page Load Speed

2.9 sec in total

First Response

137 ms

Resources Loaded

2.4 sec

Page Rendered

413 ms

flatsafe.com screenshot

About Website

Welcome to flatsafe.com homepage info - get ready to check Flat Safe best content for United States right away, or after learning these important things about flatsafe.com

FlatSafe Oklahoma Tornado Storm Shelters in OKC, Tulsa, Moore, Norman, Edmond, Yukon, Mustang, and all over the state. Underground and above ground shelters

Visit flatsafe.com

Key Findings

We analyzed Flatsafe.com page load time and found that the first response time was 137 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

flatsafe.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

flatsafe.com

137 ms

flatsafe.com

267 ms

amh1aai.js

130 ms

dashicons.min.css

74 ms

elusive.min.css

87 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 66% of them (61 requests) were addressed to the original Flatsafe.com, 9% (8 requests) were made to Use.typekit.net and 8% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Flatsafe.com.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flatsafe.com main page is 2.0 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. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 100.1 kB

  • Original 120.8 kB
  • After minification 115.9 kB
  • After compression 20.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 100.1 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 14.1 kB

  • Original 1.1 MB
  • After minification 1.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. Flat Safe images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 11.3 kB

  • Original 569.2 kB
  • After minification 569.2 kB
  • After compression 557.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.

CSS Optimization

-13%

Potential reduce by 31.6 kB

  • Original 238.7 kB
  • After minification 238.7 kB
  • After compression 207.2 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. Flatsafe.com needs all CSS files to be minified and compressed as it can save up to 31.6 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (65%)

Requests Now

79

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flatsafe.com

flatsafe.com

137 ms

flatsafe.com

flatsafe.com

267 ms

amh1aai.js

amh1aai.js

130 ms

dashicons.min.css

dashicons.min.css

74 ms

elusive.min.css

elusive.min.css

87 ms

font-awesome.min.css

font-awesome.min.css

88 ms

foundation-icons.min.css

foundation-icons.min.css

89 ms

genericons.min.css

genericons.min.css

89 ms

extra.min.css

extra.min.css

88 ms

magnific-popup.css

magnific-popup.css

97 ms

go_portfolio_styles.css

go_portfolio_styles.css

112 ms

js_composer.min.css

js_composer.min.css

157 ms

animate.css

animate.css

116 ms

slickmenu.min.css

slickmenu.min.css

116 ms

style.min.css

style.min.css

113 ms

style.css

style.css

123 ms

venobox.css

venobox.css

155 ms

css

css

57 ms

flatsafe.com

flatsafe.com

249 ms

jquery.min.js

jquery.min.js

175 ms

jquery-migrate.min.js

jquery-migrate.min.js

155 ms

formreset.min.css

formreset.min.css

173 ms

formsmain.min.css

formsmain.min.css

175 ms

readyclass.min.css

readyclass.min.css

174 ms

browsers.min.css

browsers.min.css

175 ms

jquery.json.min.js

jquery.json.min.js

175 ms

gravityforms.min.js

gravityforms.min.js

176 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

193 ms

go_portfolio_scripts.js

go_portfolio_scripts.js

195 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

196 ms

jquery.isotope.min.js

jquery.isotope.min.js

196 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

206 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

217 ms

js_composer_front.min.js

js_composer_front.min.js

223 ms

navigation.js

navigation.js

224 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

222 ms

venobox.min.js

venobox.min.js

231 ms

TweenMax.min.js

TweenMax.min.js

303 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

301 ms

api.js

api.js

53 ms

utils.min.js

utils.min.js

277 ms

slickmenu.min.js

slickmenu.min.js

237 ms

skrollr.min.js

skrollr.min.js

224 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

224 ms

frontend.min.js

frontend.min.js

225 ms

gtm.js

gtm.js

121 ms

storm-shelters-logo.jpg

storm-shelters-logo.jpg

416 ms

QEcxamIe1G8

QEcxamIe1G8

233 ms

okc-storm-shelters.png

okc-storm-shelters.png

868 ms

header-background.jpg

header-background.jpg

77 ms

icons.png

icons.png

74 ms

icon-play-black.png

icon-play-black.png

74 ms

tornado-shelters-oklahoma-city.jpg

tornado-shelters-oklahoma-city.jpg

75 ms

storm-shelters-oklahoma.jpg

storm-shelters-oklahoma.jpg

75 ms

storm-shelters-tulsa.jpg

storm-shelters-tulsa.jpg

75 ms

oklahoma-city-tornado-shelter.png

oklahoma-city-tornado-shelter.png

140 ms

storm-safe-shelters-okc.png

storm-safe-shelters-okc.png

108 ms

tornado-shelters-oklahoma.png

tornado-shelters-oklahoma.png

139 ms

underground-storm-shelter-okc.png

underground-storm-shelter-okc.png

139 ms

FEMA-storm-shelter.png

FEMA-storm-shelter.png

107 ms

NPC-tornado-shelter.jpg

NPC-tornado-shelter.jpg

106 ms

safe-rooms-NWI.jpg

safe-rooms-NWI.jpg

138 ms

flatsafe-logo.jpg

flatsafe-logo.jpg

139 ms

checkmark.png

checkmark.png

68 ms

www-player.css

www-player.css

87 ms

www-embed-player.js

www-embed-player.js

178 ms

base.js

base.js

463 ms

recaptcha__en.js

recaptcha__en.js

608 ms

d

d

108 ms

d

d

178 ms

d

d

527 ms

d

d

193 ms

d

d

194 ms

d

d

193 ms

d

d

193 ms

bg-index-section-3.jpg

bg-index-section-3.jpg

492 ms

modernizr.js

modernizr.js

92 ms

QEcxamIe1G8

QEcxamIe1G8

220 ms

base.js

base.js

42 ms

p.gif

p.gif

361 ms

ad_status.js

ad_status.js

378 ms

fallback

fallback

160 ms

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

134 ms

embed.js

embed.js

36 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

213 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

218 ms

fallback__ltr.css

fallback__ltr.css

190 ms

css

css

20 ms

id

id

14 ms

Create

Create

26 ms

logo_48.png

logo_48.png

9 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

93 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

92 ms

Accessibility Review

flatsafe.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

flatsafe.com 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

Page has valid source maps

SEO Factors

flatsafe.com SEO score

93

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

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 Flatsafe.com 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 Flatsafe.com 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

flatsafe.com

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