4 sec in total
138 ms
3.3 sec
543 ms
Click here to check amazing Excentus content for United States. Otherwise, check out these important facts you probably never knew about excentus.com
PDI, the leader in enterprise management software for the convenience retail and petroleum wholesale markets, delivers solutions for intelligent business.
Visit excentus.comWe analyzed Excentus.com page load time and found that the first response time was 138 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
excentus.com performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value18.8 s
0/100
25%
Value9.4 s
12/100
10%
Value630 ms
47/100
30%
Value0
100/100
15%
Value15.1 s
7/100
10%
138 ms
230 ms
110 ms
68 ms
81 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Excentus.com, 75% (48 requests) were made to Ed0c37be21f8ad72418b-ae99f0738c1a4f0c153c7aecac9360e1.ssl.cf1.rackcdn.com and 6% (4 requests) were made to My.excentus.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Ed0c37be21f8ad72418b-ae99f0738c1a4f0c153c7aecac9360e1.ssl.cf1.rackcdn.com.
Page size can be reduced by 264.5 kB (38%)
689.2 kB
424.7 kB
In fact, the total size of Excentus.com main page is 689.2 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. 35% of websites need less resources to load. Images take 327.6 kB which makes up the majority of the site volume.
Potential reduce by 182 B
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 46 B, which is 11% 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 182 B or 43% of the original size.
Potential reduce by 878 B
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. Excentus images are well optimized though.
Potential reduce by 113.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 113.6 kB or 59% of the original size.
Potential reduce by 149.8 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. Excentus.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 88% of the original size.
Number of requests can be reduced by 7 (12%)
59
52
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Excentus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
excentus.com
138 ms
excentus
230 ms
110 ms
css
68 ms
css
81 ms
foundation.css
398 ms
excentusweb-global.css
121 ms
webtrends.js
215 ms
n7v6
560 ms
excentusweb-Excentus-Logo-Color.svg
307 ms
excentusweb-bg-white-fueling.jpg
406 ms
excentusweb-familyincar2.jpg
425 ms
excentusweb-fuelrewards.svg
508 ms
excentusweb-centego.svg
1325 ms
excentusweb-arrow-left.svg
452 ms
Shell2.svg
570 ms
MC.svg
1285 ms
THD.svg
681 ms
TRU.svg
1288 ms
JCP.svg
1275 ms
OG.svg
1282 ms
TR.svg
1280 ms
MF.svg
1290 ms
kmart.svg
1291 ms
safeway.png
1288 ms
supervalu.png
1296 ms
ahold.png
1295 ms
gianteagle.svg
1509 ms
sunoco.png
1508 ms
WD.svg
1631 ms
bi-lo.svg
1436 ms
IGS.svg
1504 ms
verde.svg
1584 ms
harveys.svg
1771 ms
hyvee.svg
1537 ms
homeland.svg
1767 ms
countrymart.svg
1830 ms
udf.png
1725 ms
ingles.png
1726 ms
rutters.png
1870 ms
cubfoods.png
1919 ms
weis.png
1931 ms
brookshires.png
2067 ms
spinx.png
1950 ms
analytics.js
95 ms
tops.png
1907 ms
b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf
68 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
69 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
70 ms
collect
71 ms
holiday.png
1754 ms
highs.png
1704 ms
harmons.png
1628 ms
excentusweb-arrow-right.svg
1765 ms
excentusweb-american.jpg
1677 ms
piUtils.js
130 ms
excentusweb-millenial.jpg
1610 ms
excentusweb-road.jpg
1541 ms
pd.js
178 ms
excentusweb-whitepaper-clo3.jpg
1114 ms
excentusweb-whitepaper.png
1058 ms
excentusweb-driving3.jpg
1129 ms
excentusweb-superhero.jpg
1128 ms
analytics
134 ms
excentus.com accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
excentus.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
excentus.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Excentus.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 Excentus.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.
excentus.com
Open Graph description is not detected on the main page of Excentus. 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: