1.4 sec in total
216 ms
831 ms
334 ms
Welcome to weider.com homepage info - get ready to check Weider best content for United States right away, or after learning these important things about weider.com
Sports Nutrition Company specializing in Nutritional Supplements for you to live a stronger, healthier, and better life.
Visit weider.comWe analyzed Weider.com page load time and found that the first response time was 216 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.
weider.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value8.7 s
1/100
25%
Value14.7 s
1/100
10%
Value2,360 ms
5/100
30%
Value0.779
5/100
15%
Value20.8 s
2/100
10%
216 ms
57 ms
18 ms
56 ms
44 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Weider.com, 83% (54 requests) were made to Cdn.shopify.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source S3-us-west-1.amazonaws.com.
Page size can be reduced by 289.5 kB (25%)
1.2 MB
891.5 kB
In fact, the total size of Weider.com 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. 60% of websites need less resources to load. Images take 816.8 kB which makes up the majority of the site volume.
Potential reduce by 34.2 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 12.7 kB, which is 31% 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 34.2 kB or 84% of the original size.
Potential reduce by 24.5 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. Weider images are well optimized though.
Potential reduce by 176.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 176.6 kB or 68% of the original size.
Potential reduce by 54.3 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. Weider.com needs all CSS files to be minified and compressed as it can save up to 54.3 kB or 83% of the original size.
Number of requests can be reduced by 16 (26%)
62
46
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weider. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
weider.com
216 ms
theme.css
57 ms
light.css
18 ms
css
56 ms
jquery-1.6.4.min.js
44 ms
jquery.imagesloaded.min.js
19 ms
jquery.jscrollpane.min.js
53 ms
jquery.slides.min.js
52 ms
jquery.cycle.all.js
51 ms
jquery.mousewheel.min.js
52 ms
jquery.tools-tabs.min.js
78 ms
jquery.easing.min.js
81 ms
option_selection-04f21dade47c181126ac61b64d757485f84671daadfa90e4956a522cda4c2948.js
82 ms
app.js
79 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
80 ms
widgets.js
5 ms
plusone.js
179 ms
shopify_stats.js
37 ms
analytics.js
52 ms
logo.png
16 ms
search_whi.png
20 ms
header_bg_whi.png
21 ms
nav_arrow_blk.gif
22 ms
cart_icon_whi.png
18 ms
fp_slider_loader_whi.gif
23 ms
slide1_image.jpg
87 ms
fp_tabs_bg_whi.png
25 ms
fp_tabs_active_whi.png
25 ms
nav_thumb_highlight.png
27 ms
PURE-Plantlife-Bag-Render-VANILLA_compact.png
68 ms
PURE-Plantlife-Bag-Render-VANILLA_medium.png
72 ms
50509_100_Whey_Choc_Render_compact.jpg
70 ms
50509_100_Whey_Choc_Render_medium.jpg
70 ms
Diet_Render_compact.jpg
68 ms
Diet_Render_medium.jpg
71 ms
AminoSpark_WMelon_Render_compact.jpg
87 ms
AminoSpark_WMelon_Render_medium.jpg
88 ms
50505_GC6000_LemLime_Render_compact.jpg
90 ms
50505_GC6000_LemLime_Render_medium.jpg
88 ms
50490_MM4K_Choc_2700_Render_compact.jpg
85 ms
50490_MM4K_Choc_2700_Render_medium.jpg
87 ms
50485_MM2K_Choc_900_Render_compact.jpg
91 ms
50485_MM2K_Choc_900_Render_medium.jpg
97 ms
50506-1_ProCarb_Choc_Render_compact.jpg
90 ms
50506-1_ProCarb_Choc_Render_medium.jpg
91 ms
Wdr_GarcCamb_Render_compact.jpg
92 ms
Wdr_GarcCamb_Render_medium.jpg
93 ms
productimage-picture-fat-burners-16_jpg_180x225_q85_compact.jpg
95 ms
productimage-picture-fat-burners-16_jpg_180x225_q85_medium.jpg
98 ms
300ct_compact.jpg
96 ms
300ct_medium.jpg
99 ms
1px_divider_whi.gif
98 ms
promo1_thumb.jpg
99 ms
recent_posts_navi_whi.png
99 ms
button_bg_whi.gif
92 ms
visa_ico.png
91 ms
mastercard_ico.png
88 ms
amex_ico.png
88 ms
social_icons_whi.png
88 ms
collect
38 ms
cb=gapi.loaded_0
30 ms
wZLYhRRxZWGToTRP78bqJQ.woff
31 ms
UnXpojilM3XslYxUnWuVe_esZW2xOQ-xsNqO47m55DA.woff
48 ms
record.gif
61 ms
powr_temp.js
395 ms
weider.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 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.
ARIA toggle fields do not have accessible names
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
weider.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
weider.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Weider.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 Weider.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.
weider.com
Open Graph description is not detected on the main page of Weider. 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: