Tools & Wizards About Us
oilsalvage.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

oilsalvage.com

Home - Oil Salvage

Page Load Speed

2.2 sec in total

First Response

245 ms

Resources Loaded

1.4 sec

Page Rendered

547 ms

oilsalvage.com screenshot

About Website

Click here to check amazing Oil Salvage content. Otherwise, check out these important facts you probably never knew about oilsalvage.com

Oil Salvage Ltd is the largest waste oil collection company in the UK.We provide our customers with a one-stop shop for their garage waste disposal.

Visit oilsalvage.com

Key Findings

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

Performance Metrics

oilsalvage.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

oilsalvage.com

245 ms

oilsalvage.com

87 ms

autoptimize_f9f3448296eef9e569fb37a72511cd1e.css

67 ms

hubdash-tracker.js

419 ms

css

42 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 66% of them (52 requests) were addressed to the original Oilsalvage.com, 22% (17 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (617 ms) relates to the external source Stg-osllegacy-oilsalvage.kinsta.cloud.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

966.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Oilsalvage.com main page is 1.1 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. 70% of websites need less resources to load. Images take 729.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 75.6 kB

  • Original 97.3 kB
  • After minification 97.2 kB
  • After compression 21.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 75.6 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 9.3 kB

  • Original 729.1 kB
  • After minification 719.7 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. Oil Salvage images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 19.4 kB

  • Original 243.9 kB
  • After minification 243.9 kB
  • After compression 224.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 50 (86%)

Requests Now

58

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oilsalvage.com

oilsalvage.com

245 ms

oilsalvage.com

oilsalvage.com

87 ms

autoptimize_f9f3448296eef9e569fb37a72511cd1e.css

autoptimize_f9f3448296eef9e569fb37a72511cd1e.css

67 ms

hubdash-tracker.js

hubdash-tracker.js

419 ms

css

css

42 ms

jquery.min.js

jquery.min.js

50 ms

jquery-migrate.min.js

jquery-migrate.min.js

39 ms

slick.min.js

slick.min.js

43 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

46 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

51 ms

wp-polyfill.min.js

wp-polyfill.min.js

104 ms

autop.min.js

autop.min.js

105 ms

blob.min.js

blob.min.js

105 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

105 ms

react.min.js

react.min.js

105 ms

hooks.min.js

hooks.min.js

106 ms

deprecated.min.js

deprecated.min.js

113 ms

dom.min.js

dom.min.js

113 ms

react-dom.min.js

react-dom.min.js

114 ms

escape-html.min.js

escape-html.min.js

114 ms

element.min.js

element.min.js

113 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

121 ms

i18n.min.js

i18n.min.js

130 ms

keycodes.min.js

keycodes.min.js

128 ms

priority-queue.min.js

priority-queue.min.js

134 ms

compose.min.js

compose.min.js

151 ms

private-apis.min.js

private-apis.min.js

136 ms

redux-routine.min.js

redux-routine.min.js

147 ms

data.min.js

data.min.js

154 ms

html-entities.min.js

html-entities.min.js

156 ms

shortcode.min.js

shortcode.min.js

160 ms

blocks.min.js

blocks.min.js

171 ms

we-posts-slider.js

we-posts-slider.js

174 ms

css2

css2

37 ms

widget.js

widget.js

42 ms

frontend.blocks.js

frontend.blocks.js

183 ms

coblocks-animation.js

coblocks-animation.js

181 ms

tiny-swiper.js

tiny-swiper.js

180 ms

coblocks-tinyswiper-initializer.js

coblocks-tinyswiper-initializer.js

187 ms

index.js

index.js

195 ms

index.js

index.js

197 ms

api.js

api.js

48 ms

url.min.js

url.min.js

209 ms

api-fetch.min.js

api-fetch.min.js

176 ms

ultp.min.js

ultp.min.js

179 ms

glider.min.js

glider.min.js

176 ms

osl.js

osl.js

186 ms

theme.min.js

theme.min.js

179 ms

css

css

40 ms

index.js

index.js

144 ms

complianz.min.js

complianz.min.js

138 ms

gtm.js

gtm.js

197 ms

company-logo.svg

company-logo.svg

133 ms

client-logos-edited.png

client-logos-edited.png

617 ms

Untitled-design-870x570.png

Untitled-design-870x570.png

127 ms

Untitled-design-1-870x570.png

Untitled-design-1-870x570.png

142 ms

Untitled-design-1-870x570.png

Untitled-design-1-870x570.png

143 ms

company-logo-white.svg

company-logo-white.svg

106 ms

recaptcha__en.js

recaptcha__en.js

117 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

62 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

87 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

158 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

157 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

159 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

160 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

159 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

160 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

159 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

163 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

160 ms

fa-solid-900.woff

fa-solid-900.woff

235 ms

fa-regular-400.woff

fa-regular-400.woff

163 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

160 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

162 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

162 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

161 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

162 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

163 ms

tracking.js

tracking.js

77 ms

Accessibility Review

oilsalvage.com accessibility score

81

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.

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

ARIA IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

oilsalvage.com best practices score

92

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

SEO Factors

oilsalvage.com SEO score

86

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

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

    EN

  • Encoding

    UTF-8

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

oilsalvage.com

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