7.2 sec in total
1.9 sec
4.3 sec
1.1 sec
Welcome to trivita.com homepage info - get ready to check Tri Vita best content for United States right away, or after learning these important things about trivita.com
TriVita -
Visit trivita.comWe analyzed Trivita.com page load time and found that the first response time was 1.9 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
trivita.com performance score
name
value
score
weighting
Value15.9 s
0/100
10%
Value30.0 s
0/100
25%
Value24.0 s
0/100
10%
Value3,470 ms
2/100
30%
Value0.323
35/100
15%
Value33.8 s
0/100
10%
1880 ms
73 ms
132 ms
128 ms
344 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 86% of them (125 requests) were addressed to the original Trivita.com, 2% (3 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Trivita.com.
Page size can be reduced by 2.5 MB (70%)
3.5 MB
1.1 MB
In fact, the total size of Trivita.com main page is 3.5 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. 75% 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 490.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. 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 490.4 kB or 86% of the original size.
Potential reduce by 7 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. Tri Vita images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 68% of the original size.
Potential reduce by 674.2 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. Trivita.com needs all CSS files to be minified and compressed as it can save up to 674.2 kB or 84% of the original size.
Number of requests can be reduced by 117 (84%)
140
23
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tri Vita. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 93 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.trivita.com
1880 ms
js
73 ms
fbevents.js
132 ms
bat.js
128 ms
formidableforms.css
344 ms
style-blocks.build.css
244 ms
extendify-utilities.css
248 ms
main.css
190 ms
vertex-connector-public.css
190 ms
alertify.css
251 ms
theme.css
279 ms
wr-elements.min.css
250 ms
lws_icons.css
258 ms
lwsdial.min.css
292 ms
freeproduct.min.css
290 ms
proof.css
294 ms
popups.css
314 ms
holler-pro.css
312 ms
frontend.min.css
354 ms
animate.min.css
170 ms
morphext.css
319 ms
text_effects.css
328 ms
sv-wc-payment-gateway-payment-form.min.css
350 ms
wc-cybersource.min.css
351 ms
flatsome-swatches-frontend.css
355 ms
flatsome.css
424 ms
flatsome-shop.css
371 ms
style.css
381 ms
css
169 ms
wp-polyfill-inert.min.js
385 ms
regenerator-runtime.min.js
387 ms
wp-polyfill.min.js
446 ms
hooks.min.js
405 ms
w.js
167 ms
frontend-gtag.min.js
414 ms
jquery.min.js
470 ms
jquery-migrate.min.js
415 ms
vertex-connector-public.js
445 ms
alertify.min.js
489 ms
Popup.js
493 ms
PopupConfig.js
494 ms
PopupBuilder.js
495 ms
js
117 ms
js
78 ms
187059083.js
63 ms
jquery.blockUI.min.js
324 ms
js.cookie.min.js
324 ms
187059083
77 ms
core.min.js
269 ms
lwsdial.js
266 ms
frontend.min.js
263 ms
proof.min.js
274 ms
clarity.js
17 ms
wc-blocks.css
867 ms
add-to-cart.min.js
854 ms
woocommerce.min.js
848 ms
sourcebuster.min.js
844 ms
order-attribution.min.js
841 ms
react.min.js
843 ms
deprecated.min.js
835 ms
dom.min.js
822 ms
react-dom.min.js
819 ms
escape-html.min.js
807 ms
element.min.js
788 ms
is-shallow-equal.min.js
796 ms
i18n.min.js
794 ms
keycodes.min.js
795 ms
priority-queue.min.js
793 ms
compose.min.js
774 ms
private-apis.min.js
866 ms
redux-routine.min.js
866 ms
data.min.js
867 ms
lodash.min.js
848 ms
wc-blocks-registry.js
834 ms
url.min.js
835 ms
api-fetch.min.js
810 ms
g.gif
39 ms
wc-settings.js
788 ms
data-controls.min.js
786 ms
html-entities.min.js
761 ms
notices.min.js
762 ms
wc-blocks-middleware.js
762 ms
wc-blocks-data.js
764 ms
dom-ready.min.js
762 ms
a11y.min.js
756 ms
primitives.min.js
757 ms
warning.min.js
861 ms
blocks-components.js
861 ms
blocks-checkout.js
894 ms
868813168
803 ms
order-attribution-blocks.min.js
242 ms
freeproduct.js
241 ms
dismiss.js
239 ms
popups.min.js
272 ms
holler-pro.min.js
271 ms
underscore.min.js
272 ms
wp-util.min.js
269 ms
api-request.min.js
268 ms
frontend.min.js
279 ms
child_scripts.js
279 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
111 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
111 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
114 ms
morphext.js
275 ms
child_main.js
268 ms
flatsome-live-search.js
267 ms
hoverIntent.min.js
266 ms
flatsome.js
302 ms
flatsome-cookie-notice.js
298 ms
widget.js
261 ms
flatsome-ajax-add-to-cart-frontend.js
285 ms
jquery.payment.min.js
199 ms
sv-wc-payment-gateway-payment-form.js
196 ms
wc-cybersource.min.js
194 ms
flatsome-swatches-frontend.js
228 ms
smush-lazy-load.min.js
229 ms
woocommerce.js
233 ms
user-journey.js
232 ms
cart-fragments.min.js
226 ms
frm.min.js
254 ms
chat.min.js
263 ms
DebugReport.js
262 ms
formidable-abandonment.min.js
285 ms
fl-icons.ttf
259 ms
Inflammatory.png
356 ms
Bone.png
415 ms
1730110387-780db795c40a8cf9c36676eb6c8318621dc9b724e24bff21efa8f72c3037a83f-d
79 ms
Heart.png
313 ms
Immune.png
315 ms
Digestion.png
313 ms
BrainHealth.png
312 ms
muscle.png
313 ms
Vision.png
285 ms
Sleep.png
284 ms
MenWomen.png
285 ms
Energy.png
285 ms
Skin.png
285 ms
Nutritional-Support.png
280 ms
underline.png
280 ms
trivita-wellness-logo-color-470X188.png
202 ms
7863-lrg-280x280.png
202 ms
widget_app_base_1714479274721.js
134 ms
flatsome.js
108 ms
3740-lrg-280x280.png
37 ms
c.gif
8 ms
trivita.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Links do not have a discernible name
trivita.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
trivita.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
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 Trivita.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 Trivita.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.
trivita.com
Open Graph data is detected on the main page of Tri Vita. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: