9.3 sec in total
979 ms
7.8 sec
556 ms
Visit caltex.com now to see the best up-to-date Caltex content for Singapore and also check out these interesting facts you probably never knew about caltex.com
Learn about Caltex Singapore's high quality products and services ranging from Techron Fuels to Lubricants, petrol stations and Caltex Cards.
Visit caltex.comWe analyzed Caltex.com page load time and found that the first response time was 979 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
caltex.com performance score
name
value
score
weighting
Value14.1 s
0/100
10%
Value38.8 s
0/100
25%
Value24.6 s
0/100
10%
Value2,280 ms
5/100
30%
Value0.163
72/100
15%
Value36.8 s
0/100
10%
979 ms
476 ms
490 ms
99 ms
486 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 71% of them (70 requests) were addressed to the original Caltex.com, 5% (5 requests) were made to Google.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Caltex.com.
Page size can be reduced by 139.5 kB (23%)
611.3 kB
471.9 kB
In fact, the total size of Caltex.com main page is 611.3 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. 80% 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. Javascripts take 511.0 kB which makes up the majority of the site volume.
Potential reduce by 83.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. This page needs HTML code to be minified as it can gain 19.3 kB, which is 19% 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 83.8 kB or 84% of the original size.
Potential reduce by 55.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 55.6 kB or 11% of the original size.
Number of requests can be reduced by 38 (43%)
88
50
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caltex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.caltex.com
979 ms
sg
476 ms
sg
490 ms
gtm.js
99 ms
headlibs.min.css
486 ms
csrf.min.js
725 ms
csrf.min.js
722 ms
headlibs.min.js
723 ms
dependencies-es.min.css
967 ms
dependencies-es.min.js
1216 ms
forms.min.css
1256 ms
forms.min.js
2657 ms
clientlibs-commons.min.css
962 ms
clientlibs-commons.min.js
976 ms
ebOneTag.js
39 ms
satelliteLib-fec8eaa2f3fe2535cce90d8dec8fcf4775f3533a.js
36 ms
clientlibs-headerlibs.min.css
1206 ms
clientlibs-jquery.min.js
1450 ms
clientlibs-headerlibs.min.js
1254 ms
clientlibs-footerlibs.min.css
1445 ms
api.js
50 ms
iframe_api
58 ms
collect.js
34 ms
js
47 ms
analytics.js
18 ms
collect
96 ms
collect
44 ms
ga-audiences
64 ms
token.json
737 ms
5111
24 ms
analytics.js
114 ms
collect
109 ms
fbevents.js
108 ms
caltex_logo.png
342 ms
sg.png
342 ms
au.png
343 ms
kh.png
342 ms
hk.png
343 ms
id.png
341 ms
my.png
490 ms
nz1.png
490 ms
pk.png
488 ms
pl.png
484 ms
sa.png
487 ms
tl.png
494 ms
vn.png
721 ms
Havoline%20Hybrid%20Web%20Masthead.jpg
1915 ms
Caltex%20Borescope-Website%20Carousel_2800x900px_Blank_FA.jpg
729 ms
Mega1.jpg
971 ms
CaltexGO%20Homepage%201400x450.png
1447 ms
CALTEXVOU_HOMEPAGEBANNER.png
1726 ms
OCBC%20CaltexGO%20_%201400x450.jpg
2137 ms
homepage-carousel-banner-for-cbs-on-caltex-b2c.jpg
969 ms
caltex-plat98.jpg
1211 ms
BusTactical_1400x450.jpg
1210 ms
1-Tonne-Truck.jpg
1689 ms
1514100209%20Caltex%20Plus!%20Campaign%20Website%20Banner%20Homepage%20Banner%201450%20x%20450%20R2.jpg
1453 ms
tcp-masthead-SG-2020.jpg
1928 ms
home_station_finder.png
1693 ms
SG-Caltex%20Station%20Journey.jpg
1930 ms
caltexGO%20thumbnail%20web.jpg
1935 ms
grabpay_Caltex_351x230.jpg
1973 ms
Grabhitch_351x230.jpg
2153 ms
OCBC%20Card%20Lockup%206%20Feb%2024.jpg
2169 ms
HSBC%20Cards.jpg
2171 ms
SCB%20Cards%20Lockup%20Main%20Page%20(New%20Simply%20Cash%20Dec22).png
2175 ms
Link_Trust_Cards_White%20background_Website.png
2222 ms
Promo2.jpg
2372 ms
logo-caltex-white%401x.png
2387 ms
collect
101 ms
recaptcha__en.js
101 ms
track_page_view
79 ms
js
211 ms
js
109 ms
js
109 ms
events.js
206 ms
www-widgetapi.js
27 ms
ga-audiences
138 ms
72 ms
38 ms
ITCFranklinGothicStdBook.woff
2074 ms
ITCFranklinGothicStdMed.woff
2087 ms
ITCFranklinGothicStdMed.woff
2086 ms
ITCFranklinGothicStdBook.woff
2134 ms
ITCFranklinGothicStdDemi.woff
2272 ms
search%20copy%202.svg
2296 ms
main.MWNkMWZjOGNjMA.js
18 ms
16 ms
19 ms
scriptlibs.js
2189 ms
icons_right@1x.svg
2171 ms
cpl-i-home.svg
2174 ms
icon-arrow-right.png
2276 ms
techron_fuels.jpg
2364 ms
Truck_RHD.jpg
2382 ms
facebook.svg
2176 ms
youtube.svg
2173 ms
twitter.svg
1944 ms
arrow.png
250 ms
caltex.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
caltex.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
caltex.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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caltex.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 Caltex.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.
caltex.com
Open Graph data is detected on the main page of Caltex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: