1.2 sec in total
73 ms
809 ms
341 ms
Click here to check amazing TUMS content for United States. Otherwise, check out these important facts you probably never knew about tums.com
Explore our range of products and learn how TUMS antacids go to work in seconds to provide fast heartburn relief. Try America's #1 antacid today!
Visit tums.comWe analyzed Tums.com page load time and found that the first response time was 73 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
tums.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value8.4 s
2/100
25%
Value5.8 s
49/100
10%
Value1,270 ms
19/100
30%
Value0.053
98/100
15%
Value13.7 s
10/100
10%
73 ms
106 ms
33 ms
66 ms
33 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 15% of them (6 requests) were addressed to the original Tums.com, 33% (13 requests) were made to I-cf65.ch-static.com and 20% (8 requests) were made to A-cf65.ch-static.com. The less responsive or slowest element that took the longest time to load (377 ms) relates to the external source I-cf65.ch-static.com.
Page size can be reduced by 113.8 kB (7%)
1.6 MB
1.5 MB
In fact, the total size of Tums.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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 103.4 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 14.9 kB, which is 12% 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 103.4 kB or 87% of the original size.
Potential reduce by 179 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. TUMS images are well optimized though.
Potential reduce by 5.1 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.
Potential reduce by 5.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. Tums.com has all CSS files already compressed.
Number of requests can be reduced by 10 (29%)
34
24
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TUMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
tums.com
73 ms
www.tums.com
106 ms
design.default.bootstrap.v0-0-1.ts202405061339.css
33 ms
head.v0-0-1.ts202405061338.js
66 ms
css
33 ms
design.default.bootstrap.v0-0-1.ts202405061338.js
143 ms
gtm.js
247 ms
datadog-rum.js
239 ms
icon-twitter.svg
187 ms
h-yt-icon.png
315 ms
haleon-logo-colour-pos.svg
166 ms
TUMS_Gummy%20Bites_Hero_Backgroung_Homepage_Desktop-swirl.png
201 ms
youtube-play-icon.png
198 ms
bottom-bg.jpg
200 ms
logo.png
199 ms
homepage-mobile-new.png
377 ms
New-dietary-Supplement.jpg
200 ms
hm-science.jpg
376 ms
tums-homepage-tile-4-desktop.png
201 ms
f-twitter.png
267 ms
f-insta.png
266 ms
f-fb.png
267 ms
f-youtube.png
269 ms
divider-shadow.png
269 ms
icon-instagram.svg
166 ms
icon-facebook.svg
263 ms
privacy-options.svg
271 ms
widget.js
365 ms
TUMS_Homepage_Tiles_Gummy_Bites.png
142 ms
TUMS_Homepage_Tiles_Upset_Stomach.png
142 ms
KFOmCnqEu92Fr1Mu4mxM.woff
66 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
133 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
135 ms
Plentyn-Bold.woff
138 ms
iframe_api
103 ms
5a2286f46f1b11eaa422f218989845bc.js
83 ms
otSDKStub.js
104 ms
widget_app_base_1715342638247.js
36 ms
www-widgetapi.js
8 ms
bdf5fbbf-44ee-47dc-974c-d86c80b155e8.json
45 ms
tums.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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
tums.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
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
tums.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tums.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 Tums.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.
tums.com
Open Graph data is detected on the main page of TUMS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: