Tools & Wizards About Us
smartoilgauge.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

smartoilgauge.com

Smart Oil Gauge™ - WiFi Connected Heating Oil Tank Level Gauge

Page Load Speed

1.2 sec in total

First Response

26 ms

Resources Loaded

916 ms

Page Rendered

306 ms

smartoilgauge.com screenshot

About Website

Welcome to smartoilgauge.com homepage info - get ready to check Smart Oil Gauge best content right away, or after learning these important things about smartoilgauge.com

Smart Oil Gauge™ is the leading Wi-Fi heating oil tank gauge. Check your fuel oil tank level from your phone. Track your usage to save money on heating oil.

Visit smartoilgauge.com

Key Findings

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

Performance Metrics

smartoilgauge.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.444

21/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

smartoilgauge.com

26 ms

www.smartoilgauge.com

104 ms

stylesheet.css

4 ms

page_template.css

11 ms

9985bedcae7240e581ebebe2f298393b.min.js

54 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 59% of them (37 requests) were addressed to the original Smartoilgauge.com, 16% (10 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (423 ms) belongs to the original domain Smartoilgauge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.7 kB (5%)

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smartoilgauge.com main page is 2.8 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 29.7 kB

  • Original 35.4 kB
  • After minification 27.4 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 8.1 kB, which is 23% 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 29.7 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 55.2 kB

  • Original 2.4 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. Smart Oil Gauge images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 37.0 kB

  • Original 254.2 kB
  • After minification 253.6 kB
  • After compression 217.2 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 37.0 kB or 15% of the original size.

CSS Optimization

-32%

Potential reduce by 30.8 kB

  • Original 96.9 kB
  • After minification 86.5 kB
  • After compression 66.0 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. Smartoilgauge.com needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (44%)

Requests Now

45

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smartoilgauge.com

smartoilgauge.com

26 ms

www.smartoilgauge.com

www.smartoilgauge.com

104 ms

stylesheet.css

stylesheet.css

4 ms

page_template.css

page_template.css

11 ms

9985bedcae7240e581ebebe2f298393b.min.js

9985bedcae7240e581ebebe2f298393b.min.js

54 ms

jquery.min.js

jquery.min.js

39 ms

font-awesome.min.css

font-awesome.min.css

40 ms

owl.carousel.min.css

owl.carousel.min.css

17 ms

sog.css

sog.css

28 ms

owl.carousel.min.js

owl.carousel.min.js

29 ms

js

js

187 ms

big_footer.css

big_footer.css

28 ms

newsletter.js

newsletter.js

27 ms

sog_sliders.js

sog_sliders.js

28 ms

css

css

39 ms

fbevents.js

fbevents.js

146 ms

ccf_logo.png

ccf_logo.png

117 ms

lyUWaNzJtTU

lyUWaNzJtTU

265 ms

api.min.js

api.min.js

194 ms

bnr.png

bnr.png

266 ms

greybck.png

greybck.png

172 ms

wifi.png

wifi.png

155 ms

laptop1.png

laptop1.png

161 ms

app_store.svg

app_store.svg

154 ms

google_play.png

google_play.png

155 ms

phonebck2.png

phonebck2.png

242 ms

product.png

product.png

172 ms

phone_my_tank.png

phone_my_tank.png

240 ms

phone_fuelsnap.png

phone_fuelsnap.png

239 ms

ss1.png

ss1.png

423 ms

l1.png

l1.png

210 ms

l2.png

l2.png

240 ms

l3.png

l3.png

259 ms

l4.png

l4.png

259 ms

bands3.png

bands3.png

261 ms

mail_icon.png

mail_icon.png

261 ms

fb.png

fb.png

262 ms

in.png

in.png

262 ms

prev.png

prev.png

263 ms

next.png

next.png

265 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

158 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

190 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

204 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

258 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

241 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

240 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

259 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

239 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

121 ms

Gotham-Light.woff

Gotham-Light.woff

263 ms

GothamThin.woff

GothamThin.woff

262 ms

Gotham-Book.woff

Gotham-Book.woff

264 ms

GothamMedium.woff

GothamMedium.woff

262 ms

GothamBold.woff

GothamBold.woff

263 ms

bundle.es5.min.js

bundle.es5.min.js

118 ms

www-player.css

www-player.css

21 ms

www-embed-player.js

www-embed-player.js

61 ms

base.js

base.js

113 ms

ad_status.js

ad_status.js

159 ms

Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js

Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js

113 ms

embed.js

embed.js

40 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

11 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

11 ms

Accessibility Review

smartoilgauge.com accessibility score

78

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

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

smartoilgauge.com SEO score

81

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

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

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

smartoilgauge.com

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