Tools & Wizards About Us
odysseyfire.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

odysseyfire.com

Odyssey Fire Protection Wilmington, NC - Odyssey Fire Protection NFPA 25 Inspections

Page Load Speed

932 ms in total

First Response

95 ms

Resources Loaded

702 ms

Page Rendered

135 ms

odysseyfire.com screenshot

About Website

Click here to check amazing Odyssey Fire content. Otherwise, check out these important facts you probably never knew about odysseyfire.com

Odyssey Fire Protection LLC designs, fabricates, installs or repairs all types of fire suppression systems. NFPA 25 inspections & 24-hour emergency service.

Visit odysseyfire.com

Key Findings

We analyzed Odysseyfire.com page load time and found that the first response time was 95 ms and then it took 837 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

odysseyfire.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.odysseyfire.com

95 ms

www.odysseyfire.com

131 ms

jquery-3.3.1.min.js

138 ms

rsrc_70b71187e32999ec386488c3bab6bf12.jsx

157 ms

font-awesome.min.css

66 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Odysseyfire.com, 25% (13 requests) were made to Static2.mysiteserver.net and 8% (4 requests) were made to Static1.mysiteserver.net. The less responsive or slowest element that took the longest time to load (195 ms) relates to the external source Static6.mysiteserver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.1 kB (9%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Odysseyfire.com main page is 1.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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 33.8 kB

  • Original 41.6 kB
  • After minification 40.1 kB
  • After compression 7.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 33.8 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 63.9 kB

  • Original 1.0 MB
  • After minification 970.6 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. Odyssey Fire images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.8 kB

  • Original 88.8 kB
  • After minification 88.8 kB
  • After compression 86.0 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

-14%

Potential reduce by 533 B

  • Original 3.7 kB
  • After minification 3.3 kB
  • After compression 3.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. Odysseyfire.com needs all CSS files to be minified and compressed as it can save up to 533 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (45%)

Requests Now

49

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.odysseyfire.com

www.odysseyfire.com

95 ms

www.odysseyfire.com

www.odysseyfire.com

131 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

138 ms

rsrc_70b71187e32999ec386488c3bab6bf12.jsx

rsrc_70b71187e32999ec386488c3bab6bf12.jsx

157 ms

font-awesome.min.css

font-awesome.min.css

66 ms

rsrc_a2d1f2fe43465216edcc6930791c8be7.cssx

rsrc_a2d1f2fe43465216edcc6930791c8be7.cssx

159 ms

jquery.min.js

jquery.min.js

158 ms

all.js

all.js

35 ms

rsrc_7d0848f44fb932ca4b7db6c4ff249686.jsx

rsrc_7d0848f44fb932ca4b7db6c4ff249686.jsx

146 ms

hoverIntent.js

hoverIntent.js

150 ms

superfish.js

superfish.js

157 ms

sprites2.js

sprites2.js

164 ms

BTMQuickDropDown.js

BTMQuickDropDown.js

189 ms

hlpr.css

hlpr.css

147 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

149 ms

jquery.validate-1.11.1.min.js

jquery.validate-1.11.1.min.js

152 ms

rsrc_f99e1e157cd58f933fb46797a446ed65.jsx

rsrc_f99e1e157cd58f933fb46797a446ed65.jsx

195 ms

rsrc_77b26e6b518c8e56a0861ac707215e89.jsx

rsrc_77b26e6b518c8e56a0861ac707215e89.jsx

144 ms

jquery.cycle.all.pack.js

jquery.cycle.all.pack.js

120 ms

rsrc_399ffdbe2b353614b4c6bb71d63c7b2d.jsx

rsrc_399ffdbe2b353614b4c6bb71d63c7b2d.jsx

180 ms

rsrc_9207de610a9f77eaad795bcea305b32d.cssx

rsrc_9207de610a9f77eaad795bcea305b32d.cssx

147 ms

site.css

site.css

162 ms

js

js

89 ms

everypage.js

everypage.js

162 ms

all.js

all.js

5 ms

142 ms

sitebg.jpg

sitebg.jpg

184 ms

logo.png

logo.png

111 ms

Untitled-2.jpgx

Untitled-2.jpgx

165 ms

Untitled-3.jpgx

Untitled-3.jpgx

171 ms

1.jpgx

1.jpgx

125 ms

2.jpgx

2.jpgx

126 ms

3.jpgx

3.jpgx

146 ms

4.jpgx

4.jpgx

144 ms

navbg.png

navbg.png

94 ms

Untitled-1.jpgx

Untitled-1.jpgx

88 ms

FB.png

FB.png

117 ms

popupFormBG.png

popupFormBG.png

47 ms

masthead.jpg

masthead.jpg

80 ms

logo.png

logo.png

67 ms

Proud-PBFS-Header-Logo-1_0_light-bg.png

Proud-PBFS-Header-Logo-1_0_light-bg.png

126 ms

buttonBG.png

buttonBG.png

99 ms

lc-companies_Odyssey_Fire-v2.jpg

lc-companies_Odyssey_Fire-v2.jpg

119 ms

4.jpg

4.jpg

133 ms

slideshow-active.png

slideshow-active.png

112 ms

slideshow-off.png

slideshow-off.png

120 ms

Proud-PBFS-Header-Logo-1_0_light-bg.png

Proud-PBFS-Header-Logo-1_0_light-bg.png

157 ms

8-12-11%20aerial%20view.jpgx

8-12-11%20aerial%20view.jpgx

113 ms

5.jpgx

5.jpgx

71 ms

logo.png

logo.png

118 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20 ms

Print.css

Print.css

31 ms

Accessibility Review

odysseyfire.com accessibility score

59

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

odysseyfire.com best practices score

67

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

SEO Factors

odysseyfire.com SEO score

92

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odysseyfire.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Odysseyfire.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

odysseyfire.com

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