Tools & Wizards About Us
pottersignal.net screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% 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

  • 89

    SEO

    Google-friendlier than
    66% of websites

pottersignal.net

Potter Electric: Fire Alarms & Fire Sprinkler Systems

Page Load Speed

2.6 sec in total

First Response

171 ms

Resources Loaded

2.2 sec

Page Rendered

193 ms

pottersignal.net screenshot

About Website

Welcome to pottersignal.net homepage info - get ready to check Potter Signal best content right away, or after learning these important things about pottersignal.net

Potter Electric Signal Company is a St. Louis, Missouri based manufacturer of sprinkler monitoring devices, fire alarm systems, & corrosion solution products.

Visit pottersignal.net

Key Findings

We analyzed Pottersignal.net page load time and found that the first response time was 171 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pottersignal.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value7.2 s

29/100

10%

TBT (Total Blocking Time)

Value4,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

pottersignal.net

171 ms

www.pottersignal.com

316 ms

gtm.js

236 ms

bootstrap.min.css

68 ms

fontawesome.min.css

53 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pottersignal.net, 37% (25 requests) were made to Pottersignal.com and 12% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (469 ms) relates to the external source Tr.lfeeder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.0 kB (10%)

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pottersignal.net main page is 3.4 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 74.5 kB

  • Original 85.9 kB
  • After minification 56.1 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 29.8 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 74.5 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 195.2 kB

  • Original 2.6 MB
  • After minification 2.4 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. Potter Signal images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 53.1 kB

  • Original 468.8 kB
  • After minification 468.8 kB
  • After compression 415.6 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 53.1 kB or 11% of the original size.

CSS Optimization

-0%

Potential reduce by 189 B

  • Original 205.3 kB
  • After minification 205.3 kB
  • After compression 205.1 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. Pottersignal.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

52

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pottersignal.net

pottersignal.net

171 ms

www.pottersignal.com

www.pottersignal.com

316 ms

gtm.js

gtm.js

236 ms

bootstrap.min.css

bootstrap.min.css

68 ms

fontawesome.min.css

fontawesome.min.css

53 ms

all.min.css

all.min.css

121 ms

main.min.css

main.min.css

107 ms

yamm.css

yamm.css

110 ms

css

css

65 ms

css

css

77 ms

satelliteLib-4af1f0fca3c1cac2f2ec2ec62ba1a5a6f252d25c.js

satelliteLib-4af1f0fca3c1cac2f2ec2ec62ba1a5a6f252d25c.js

73 ms

index.css

index.css

109 ms

jquery.min.js

jquery.min.js

71 ms

jquery-ui.min.js

jquery-ui.min.js

75 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

108 ms

bootstrap.min.js

bootstrap.min.js

76 ms

main.min.js

main.min.js

225 ms

api.js

api.js

73 ms

UEOdX_UzuYs

UEOdX_UzuYs

181 ms

header-logo.svg

header-logo.svg

132 ms

nav-logo.svg

nav-logo.svg

129 ms

nav-bg.jpg

nav-bg.jpg

129 ms

nav-logo.png

nav-logo.png

138 ms

kkr.jpg

kkr.jpg

131 ms

integrated%20amp.png

integrated%20amp.png

464 ms

LED-banner.png

LED-banner.png

139 ms

IntegratedAmp.png

IntegratedAmp.png

315 ms

intellicom-carousel.jpg

intellicom-carousel.jpg

138 ms

pfc-4410g3.png

pfc-4410g3.png

271 ms

D-Tect_Carousel_Banner.png

D-Tect_Carousel_Banner.png

270 ms

sub-footer-logo.svg

sub-footer-logo.svg

208 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

133 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff

134 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff

135 ms

www-player.css

www-player.css

72 ms

www-embed-player.js

www-embed-player.js

100 ms

base.js

base.js

326 ms

js

js

169 ms

destination

destination

222 ms

analytics.js

analytics.js

219 ms

insight.min.js

insight.min.js

216 ms

lftracker_v1_YEgkB8lXYNy8ep3Z.js

lftracker_v1_YEgkB8lXYNy8ep3Z.js

211 ms

pd.js

pd.js

282 ms

fa-solid-900.ttf

fa-solid-900.ttf

207 ms

fa-regular-400.ttf

fa-regular-400.ttf

280 ms

fa-light-300.ttf

fa-light-300.ttf

280 ms

fa-thin-100.ttf

fa-thin-100.ttf

280 ms

NaPecZTIAOhVxoMyOr9n_E7fdMPmC6ZRbrw.woff

NaPecZTIAOhVxoMyOr9n_E7fdMPmC6ZRbrw.woff

96 ms

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZZabuWI.woff

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZZabuWI.woff

118 ms

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZZabuWI.woff

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZZabuWI.woff

184 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

116 ms

fa-brands-400.ttf

fa-brands-400.ttf

277 ms

iframe_api

iframe_api

67 ms

www-widgetapi.js

www-widgetapi.js

157 ms

insight.old.min.js

insight.old.min.js

61 ms

collect

collect

423 ms

ad_status.js

ad_status.js

255 ms

analytics

analytics

378 ms

tr.lfeeder.com

tr.lfeeder.com

469 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

100 ms

embed.js

embed.js

36 ms

collect

collect

204 ms

id

id

158 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

160 ms

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

159 ms

Create

Create

23 ms

ga-audiences

ga-audiences

128 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

pottersignal.net accessibility score

91

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

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

pottersignal.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pottersignal.net SEO score

89

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

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 Pottersignal.net 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 Pottersignal.net 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

pottersignal.net

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