1.4 sec in total
121 ms
916 ms
342 ms
Visit exxon.com now to see the best up-to-date Exxon content for United States and also check out these interesting facts you probably never knew about exxon.com
Learn more about the reliable and trusted quality fuels and lubricant products from Exxon and Mobil.
Visit exxon.comWe analyzed Exxon.com page load time and found that the first response time was 121 ms and then it took 1.3 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.
exxon.com performance score
name
value
score
weighting
Value2.9 s
55/100
10%
Value11.0 s
0/100
25%
Value5.1 s
61/100
10%
Value400 ms
67/100
30%
Value0.56
12/100
15%
Value10.3 s
25/100
10%
121 ms
69 ms
8 ms
15 ms
6 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 47% of them (42 requests) were addressed to the original Exxon.com, 4% (4 requests) were made to P.rfihub.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (363 ms) relates to the external source Exxonmobilstations.com.
Page size can be reduced by 786.9 kB (48%)
1.6 MB
856.3 kB
In fact, the total size of Exxon.com main page is 1.6 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. 60% of websites need less resources to load. Images take 748.4 kB which makes up the majority of the site volume.
Potential reduce by 38.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. This page needs HTML code to be minified as it can gain 8.6 kB, which is 18% 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 38.0 kB or 82% of the original size.
Potential reduce by 144.4 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. Obviously, Exxon needs image optimization as it can save up to 144.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 259.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 259.2 kB or 60% of the original size.
Potential reduce by 345.3 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. Exxon.com needs all CSS files to be minified and compressed as it can save up to 345.3 kB or 83% of the original size.
Number of requests can be reduced by 38 (49%)
77
39
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Exxon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
exxon.com
121 ms
www.exxon.com
69 ms
iemobile.js
8 ms
front.main.css
15 ms
font-awesome.min.css
6 ms
modernizr.min.js
12 ms
application.min.js
11 ms
analytics.js
26 ms
jquery.min.js
17 ms
logo-exxon-mobil.png
11 ms
app-store.png
12 ms
google-play.png
11 ms
32690_exxmo_energy_p3_1400x490.jpg
90 ms
homepagecta6.jpg
87 ms
car-tips.jpeg
88 ms
card_text_background.png
96 ms
32641_scard_copy_592x146-final.png
92 ms
fueltip.png
91 ms
fueltip-plus-small.png
88 ms
fueltip-icon-weight.png
90 ms
fueltip-icon-share.png
92 ms
fueltip-icon-takeout.png
92 ms
fueltip-icon-tire.png
94 ms
fueltip-plus.png
92 ms
fueltip-mobile-image1.png
97 ms
fueltip-mobile-image2.png
94 ms
fueltip-mobile-image3.png
96 ms
fueltip-mobile-image4.png
99 ms
fueltip-arrow-left.png
98 ms
fueltip-arrow-right.png
95 ms
video-holder.jpg
97 ms
bkg_aspiration-11.00.55-am.jpeg
103 ms
energyquiz_round2.png
98 ms
facebook-sml.png
98 ms
foot-exxonMobil-on.png
99 ms
foot-exxon-on.png
101 ms
foot-mobil-on.png
101 ms
foot-esso-on.png
100 ms
foot-xto-on.png
101 ms
EMprintW01-Regular.woff
98 ms
gap.min.js
77 ms
tc.min.js
73 ms
webservice.php
363 ms
iframe_api
142 ms
fontawesome-webfont.woff
28 ms
EMprintW01-Semibold.woff
30 ms
EMprintW01-Light.woff
37 ms
EMprintW01-RegularItalic.woff
28 ms
ca.html
17 ms
ga.js
34 ms
pixel
20 ms
Pug
52 ms
cx
65 ms
rum
44 ms
adb.gif
52 ms
1
52 ms
cs
360 ms
demconf.jpg
39 ms
pixel
45 ms
__utm.gif
32 ms
rum
27 ms
sd
24 ms
cm
24 ms
360947.gif
25 ms
sync
23 ms
xrefid.xgi
26 ms
28 ms
pixel
40 ms
cm
28 ms
mapuid
34 ms
www-widgetapi.js
64 ms
cm
28 ms
cx
38 ms
collect
74 ms
cm
33 ms
33 ms
xrefid.xgi
20 ms
362378.gif
20 ms
cx
21 ms
lr.gif
7 ms
pixel.gif
124 ms
DXwAKIfq_U4
57 ms
pixel.gif
18 ms
tap.php
237 ms
www-embed-player-vflZsBgOl.css
20 ms
www-embed-player.js
41 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
25 ms
ad_status.js
31 ms
US_smap.png
260 ms
exxon.com accessibility score
exxon.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
exxon.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exxon.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 Exxon.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.
exxon.com
Open Graph data is detected on the main page of Exxon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: