2.5 sec in total
94 ms
2.1 sec
342 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 94 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
tums.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value7.4 s
4/100
25%
Value5.7 s
51/100
10%
Value860 ms
33/100
30%
Value0.741
6/100
15%
Value12.4 s
14/100
10%
94 ms
199 ms
260 ms
284 ms
199 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 68% of them (47 requests) were addressed to the original Tums.com, 7% (5 requests) were made to Nexus.ensighten.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (562 ms) belongs to the original domain Tums.com.
Page size can be reduced by 1.2 MB (39%)
3.0 MB
1.9 MB
In fact, the total size of Tums.com main page is 3.0 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 28.3 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 28.3 kB or 83% of the original size.
Potential reduce by 488.8 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, TUMS needs image optimization as it can save up to 488.8 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 66.7 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 66.7 kB or 48% of the original size.
Potential reduce by 598.5 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 needs all CSS files to be minified and compressed as it can save up to 598.5 kB or 88% of the original size.
Number of requests can be reduced by 31 (53%)
58
27
The browser has sent 58 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 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
tums.com
94 ms
tums.com
199 ms
www.tums.com
260 ms
design.grid96012le.js
284 ms
design.grid96012le.0.css
199 ms
design.grid96012le.1.css
211 ms
design.grid96012le.2.css
182 ms
design.grid96012le.3.css
141 ms
design.grid96012le.4.css
180 ms
design.grid96012le.5.css
220 ms
design.grid96012le.6.css
224 ms
design.grid96012le.7.css
221 ms
design.grid96012le.8.css
273 ms
design.grid96012le.9.css
246 ms
design.grid96012le.10.css
261 ms
Bootstrap.js
49 ms
jquery.mousewheel.min.js
78 ms
jquery.mousewheel.min.js
66 ms
homebg.png
164 ms
headerbg.png
155 ms
toggle-menu.png
61 ms
tums-logo.png
60 ms
gsk-logo.png
54 ms
searchmobile.png
62 ms
TR_Hero-Image.png
562 ms
Tums-americas-no-1-antacid.png
171 ms
TR_Strawberries.png
157 ms
TR_Tweet_Image.png
153 ms
Tums-chewy-delights-coupon.png
236 ms
Tums-smoothies-bbq.png
221 ms
Science_video.png
205 ms
video_play.png
213 ms
TR_Heartburn_fight.png
349 ms
TR_Cherries.png
265 ms
TR_Tweet.png
266 ms
TR_google.png
267 ms
TR_youtube.png
282 ms
TR_facebook.png
310 ms
TR_twitter.png
315 ms
sourcesanspro-regular-webfont.woff
310 ms
sourcesanspro-light-webfont.woff
323 ms
sourcesanspro-extralight-webfont.woff
353 ms
sourcesanspro-semibold-webfont.woff
370 ms
sourcesanspro-bold-webfont.woff
371 ms
arrowclosed.png
380 ms
navigationarrow.png
390 ms
FSAlbertPro-Bold.woff
442 ms
learnmorearrow.png
409 ms
learn.png
413 ms
FSAlbertPro-BoldItalic.woff
445 ms
serverComponent.php
65 ms
b2bf785faf8dc5ad76839caba0daef00.js
5 ms
da8390754142a83d02774b304d4fe3ce.js
20 ms
f680f1e8a57f3168acf66b9cf3641781.js
39 ms
activityi;src=3097830;type=tums;cat=slandpg;u1=tums:index;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=9757397694047.541
78 ms
iframe_api
120 ms
analytics.js
123 ms
ytc.js
365 ms
gw.js
442 ms
activityi;src=3097830;type=tums-0;cat=tums-0;ord=4264635555446.148
38 ms
dynamic_rmpixel_1710.gif
369 ms
ct.gif
95 ms
ct.gif
90 ms
redir.php
90 ms
www-widgetapi.js
65 ms
collect
13 ms
collect
54 ms
s69231214302126
82 ms
581790707.js
78 ms
tums.com 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
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
ZH
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 does not match the claimed Chinese 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 description is not detected on the main page of TUMS. 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: