Tools & Wizards About Us
empirepetroleum.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

empirepetroleum.com

Empire Petroleum Partners, LLC - Fuel and dealer services - Dallas, Texas

Page Load Speed

4 sec in total

First Response

461 ms

Resources Loaded

2.8 sec

Page Rendered

767 ms

empirepetroleum.com screenshot

About Website

Welcome to empirepetroleum.com homepage info - get ready to check Empire Petroleum best content for United States right away, or after learning these important things about empirepetroleum.com

Dallas based Empire Petroleum provides marketing, branding and inventory, helping dealers build successful fuel store businesses.

Visit empirepetroleum.com

Key Findings

We analyzed Empirepetroleum.com page load time and found that the first response time was 461 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

empirepetroleum.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value920 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

www.empirepetroleum.com

461 ms

swiper.min.css

134 ms

tippy.css

135 ms

gs-logo.min.css

135 ms

frontend.css

143 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 76% of them (75 requests) were addressed to the original Empirepetroleum.com, 10% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Empirepetroleum.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 562.2 kB (3%)

Content Size

19.5 MB

After Optimization

18.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Empirepetroleum.com main page is 19.5 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. 75% 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 19.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 81.0 kB

  • Original 101.0 kB
  • After minification 94.5 kB
  • After compression 20.0 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 81.0 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 468.7 kB

  • Original 19.0 MB
  • After minification 18.5 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. Empire Petroleum images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 297.8 kB
  • After minification 296.7 kB
  • After compression 295.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.

CSS Optimization

-9%

Potential reduce by 10.2 kB

  • Original 118.7 kB
  • After minification 118.7 kB
  • After compression 108.5 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. Empirepetroleum.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (87%)

Requests Now

84

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.empirepetroleum.com

www.empirepetroleum.com

461 ms

swiper.min.css

swiper.min.css

134 ms

tippy.css

tippy.css

135 ms

gs-logo.min.css

gs-logo.min.css

135 ms

frontend.css

frontend.css

143 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

139 ms

ai-preloader-public.css

ai-preloader-public.css

145 ms

styles.css

styles.css

203 ms

styles.min.css

styles.min.css

200 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

201 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

208 ms

widget-base.min.css

widget-base.min.css

211 ms

header-footer-elementor.css

header-footer-elementor.css

213 ms

frontend-lite.min.css

frontend-lite.min.css

268 ms

swiper.min.css

swiper.min.css

272 ms

post-8.css

post-8.css

267 ms

swiper.css

swiper.css

76 ms

venobox.min.css

venobox.min.css

276 ms

widgets-style.css

widgets-style.css

353 ms

flaticon.css

flaticon.css

281 ms

ai-animation.css

ai-animation.css

333 ms

font-awesome.min.css

font-awesome.min.css

336 ms

owl.carousel.min.css

owl.carousel.min.css

335 ms

owl.theme.default.min.css

owl.theme.default.min.css

344 ms

slick.css

slick.css

350 ms

slick-theme.css

slick-theme.css

399 ms

widget-responsive.css

widget-responsive.css

404 ms

global.css

global.css

402 ms

post-3796.css

post-3796.css

412 ms

post-410.css

post-410.css

419 ms

css2

css2

82 ms

css2

css2

99 ms

bootstrap.min.css

bootstrap.min.css

74 ms

bootstrap-icons.css

bootstrap-icons.css

82 ms

font-awesome.min.css

font-awesome.min.css

422 ms

theme-style.css

theme-style.css

466 ms

theme-responsive.css

theme-responsive.css

470 ms

style.css

style.css

471 ms

css

css

102 ms

jquery.min.js

jquery.min.js

551 ms

jquery-migrate.min.js

jquery-migrate.min.js

487 ms

ai-preloader-public.js

ai-preloader-public.js

490 ms

js

js

106 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

109 ms

swiper.js

swiper.js

26 ms

js

js

115 ms

wpstg-blank-loader.min.js

wpstg-blank-loader.min.js

474 ms

swiper.min.js

swiper.min.js

415 ms

tippy-bundle.umd.min.js

tippy-bundle.umd.min.js

410 ms

images-loaded.min.js

images-loaded.min.js

528 ms

gs-logo.min.js

gs-logo.min.js

523 ms

isotope.min.js

isotope.min.js

519 ms

carouselTicker.min.js

carouselTicker.min.js

518 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

15 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

12 ms

hooks.min.js

hooks.min.js

464 ms

i18n.min.js

i18n.min.js

462 ms

index.js

index.js

462 ms

index.js

index.js

457 ms

venobox.min.js

venobox.min.js

470 ms

tabscript.js

tabscript.js

478 ms

owl.carousel.min.js

owl.carousel.min.js

424 ms

slick.min.js

slick.min.js

444 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

537 ms

particles.min.js

particles.min.js

533 ms

widget-script.js

widget-script.js

533 ms

theme-script.js

theme-script.js

481 ms

wpsl-gmap.min.js

wpsl-gmap.min.js

479 ms

underscore-before.js

underscore-before.js

499 ms

underscore.min.js

underscore.min.js

547 ms

underscore-after.js

underscore-after.js

531 ms

webpack.runtime.min.js

webpack.runtime.min.js

538 ms

frontend-modules.min.js

frontend-modules.min.js

496 ms

waypoints.min.js

waypoints.min.js

492 ms

core.min.js

core.min.js

491 ms

frontend.min.js

frontend.min.js

538 ms

wp-util.min.js

wp-util.min.js

532 ms

frontend.min.js

frontend.min.js

523 ms

empire-logo-transparent.png

empire-logo-transparent.png

364 ms

home-main-dark.png

home-main-dark.png

771 ms

Wixom-5-1536x864.jpg

Wixom-5-1536x864.jpg

577 ms

empire-logo.png

empire-logo.png

479 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7oUXskPMU.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7oUXskPMU.ttf

47 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7oUUsj.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7oUUsj.ttf

172 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7aUXskPMU.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7aUXskPMU.ttf

147 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7aUUsj.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj7aUUsj.ttf

195 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj62UXskPMU.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj62UXskPMU.ttf

183 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj62UUsj.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj62UUsj.ttf

212 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj42VnskPMU.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj42VnskPMU.ttf

182 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj42Vksj.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj42Vksj.ttf

195 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj4PVnskPMU.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj4PVnskPMU.ttf

211 ms

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj4PVksj.ttf

V8mQoQDjQSkFtoMM3T6r8E7mF71Q-gOoraIAEj4PVksj.ttf

193 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

493 ms

bootstrap-icons.woff

bootstrap-icons.woff

22 ms

counter-bg-1.jpg

counter-bg-1.jpg

387 ms

service-bg.jpg

service-bg.jpg

336 ms

vecteezy_diversity-people-of-all-races-and-genders-together_29882162.png

vecteezy_diversity-people-of-all-races-and-genders-together_29882162.png

1218 ms

footer-bg.jpg

footer-bg.jpg

374 ms

commerce_1.png

commerce_1.png

826 ms

Accessibility Review

empirepetroleum.com accessibility score

87

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

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

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

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

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

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

empirepetroleum.com

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