Tools & Wizards About Us
gascopropane.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

gascopropane.com

Local Propane Supplier, Refill, and Delivery | Ferrellgas | Fuel Life Simply

Page Load Speed

867 ms in total

First Response

45 ms

Resources Loaded

757 ms

Page Rendered

65 ms

gascopropane.com screenshot

About Website

Welcome to gascopropane.com homepage info - get ready to check Gasco Propane best content right away, or after learning these important things about gascopropane.com

For nearly 80 years, Ferrellgas has been serving local communities as your local propane provider. Trust us to fuel what matters to you and find the location nearest to you.

Visit gascopropane.com

Key Findings

We analyzed Gascopropane.com page load time and found that the first response time was 45 ms and then it took 822 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

gascopropane.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,970 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

gascopropane.com

45 ms

201 ms

t.js

33 ms

logger.js

28 ms

fonts.css

153 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Gascopropane.com, 53% (10 requests) were made to Ferrellgas.com and 5% (1 request) were made to Cdn.trackjs.com. The less responsive or slowest element that took the longest time to load (338 ms) relates to the external source Home-c28.incontact.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.6 kB (27%)

Content Size

231.0 kB

After Optimization

169.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Gascopropane.com main page is 231.0 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. 15% of websites need less resources to load. Javascripts take 182.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 40.5 kB

  • Original 48.0 kB
  • After minification 34.6 kB
  • After compression 7.6 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 13.4 kB, which is 28% 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 40.5 kB or 84% of the original size.

JavaScript Optimization

-11%

Potential reduce by 20.5 kB

  • Original 182.0 kB
  • After minification 182.0 kB
  • After compression 161.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 20.5 kB or 11% of the original size.

CSS Optimization

-72%

Potential reduce by 637 B

  • Original 881 B
  • After minification 881 B
  • After compression 244 B

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. Gascopropane.com needs all CSS files to be minified and compressed as it can save up to 637 B or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (64%)

Requests Now

14

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gascopropane.com

gascopropane.com

45 ms

201 ms

t.js

t.js

33 ms

logger.js

logger.js

28 ms

fonts.css

fonts.css

153 ms

lde5odd.js

lde5odd.js

40 ms

css

css

139 ms

main.css

main.css

46 ms

optimize.js

optimize.js

181 ms

email-decode.min.js

email-decode.min.js

38 ms

embed.min.js

embed.min.js

338 ms

polyfills.js

polyfills.js

142 ms

index.js

index.js

137 ms

10041827-10042318.js

10041827-10042318.js

147 ms

E3D2C20994061A8E0.css

E3D2C20994061A8E0.css

187 ms

gtm.js

gtm.js

122 ms

ferrellgas_logo-white.svg

ferrellgas_logo-white.svg

62 ms

icons.woff

icons.woff

11 ms

ferrellgas.ttf

ferrellgas.ttf

16 ms

Accessibility Review

gascopropane.com accessibility score

71

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

[role] values are not valid

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

gascopropane.com best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gascopropane.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 Gascopropane.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

gascopropane.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: