2.2 sec in total
402 ms
1.5 sec
356 ms
Welcome to mobil.ph homepage info - get ready to check Mobil best content right away, or after learning these important things about mobil.ph
Explore a wide range of synthetic engine oils & lubricants for use in personal vehicles including cars & motorcycles, and industrial applications. Read more here!
Visit mobil.phWe analyzed Mobil.ph page load time and found that the first response time was 402 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
mobil.ph performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value10.8 s
0/100
25%
Value7.5 s
26/100
10%
Value1,250 ms
19/100
30%
Value0.082
94/100
15%
Value10.0 s
26/100
10%
402 ms
260 ms
91 ms
132 ms
134 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 97% of them (65 requests) were addressed to the original Mobil.ph, 3% (2 requests) were made to Sdc.exxonmobil.com. The less responsive or slowest element that took the longest time to load (402 ms) belongs to the original domain Mobil.ph.
Page size can be reduced by 634.1 kB (55%)
1.2 MB
524.8 kB
In fact, the total size of Mobil.ph main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 446.6 kB which makes up the majority of the site volume.
Potential reduce by 94.8 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 94.8 kB or 88% of the original size.
Potential reduce by 42.0 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. Mobil images are well optimized though.
Potential reduce by 338.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 338.2 kB or 76% of the original size.
Potential reduce by 159.1 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. Mobil.ph needs all CSS files to be minified and compressed as it can save up to 159.1 kB or 87% of the original size.
Number of requests can be reduced by 38 (59%)
64
26
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
default.aspx
402 ms
LCW_xom.css
260 ms
LCW_xom_web_medium.css
91 ms
LCW_styleswitcher.js
132 ms
LCW_footnotelinks.js
134 ms
LCW_xom.js
131 ms
LCW_search.js
175 ms
LCW_redesign_swfobject.js
133 ms
prototype.js
310 ms
quickedit.js
138 ms
custom.js
141 ms
scriptaculous.js
177 ms
lightview.js
270 ms
toggleContent.js
181 ms
jquery.fancybox-1.3.4.css
184 ms
EUCookieStyleMain.css
248 ms
EUCookieStyleExtend.css
248 ms
jquery-1.9.1_fromEndrosedRepo.min.js
361 ms
jquery.fancybox-1.3.4.js
264 ms
jquery.easing-1.3.pack.js
268 ms
jquery.mousewheel-3.0.4.pack.js
269 ms
EUCookiescripts_forOPT-IN-FancyBox.js
305 ms
search.js
286 ms
LCW_mobile.js
286 ms
LCW_webtrends.js
271 ms
effects.js
48 ms
headerlogo_86x30_mobil-logo_gbl.jpg
53 ms
HeaderOFF_LEFT.gif
50 ms
HeaderOFF_RIGHT.gif
48 ms
article_150x150_porsche-panamera_gbl.jpg
53 ms
callout_90x90_ball-bearing.jpg
51 ms
teaser_90x90_euro-truck_eame.jpg
50 ms
retina-viz.jpg
357 ms
retina-exxonmobil.png
95 ms
retina-mobil.png
96 ms
retina-esso.png
94 ms
retina-xto.png
95 ms
ftrCountries.jpg
57 ms
leftSideBtn.jpg
91 ms
rightSideBtn.jpg
92 ms
middleBtn.jpg
89 ms
HeaderOff.gif
84 ms
media_615x274_homepage-flash-banner-cycler.gif
121 ms
calloutFrame1000.gif
129 ms
metalBg.jpg
128 ms
hdrBarCir.gif
104 ms
hdrBarArowOff.gif
97 ms
homeBanner600.gif
202 ms
teaser_60x60_atf-200.png
203 ms
expandoButton.jpg
207 ms
teaser_90x90_map_gbl.jpg
208 ms
search-button.png
205 ms
wtid.js
117 ms
EMprint-Regular.woff
195 ms
carengineoils.html
59 ms
heavydutyoils.html
74 ms
industrialspecialty.html
85 ms
wheretobuy.html
86 ms
mobilbrands.html
95 ms
fuels.html
97 ms
blank.gif
84 ms
fancybox.png
82 ms
dcs.gif
81 ms
industrialspeciality.html
50 ms
LCW_xom_print.css
46 ms
LCW_xom_web_large.css
46 ms
LCW_xom_web_small.css
46 ms
mobil.ph accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
mobil.ph 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
mobil.ph 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 Mobil.ph 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 Mobil.ph 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.
mobil.ph
Open Graph description is not detected on the main page of Mobil. 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: