3.3 sec in total
280 ms
2.6 sec
379 ms
Visit core150.com now to see the best up-to-date Core150 content and also check out these interesting facts you probably never knew about core150.com
The Core150 protein shake bottle. A 1L shaker cup with three 50g storage compartments for your pre, intra, and post workout hydration.
Visit core150.comWe analyzed Core150.com page load time and found that the first response time was 280 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
core150.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value8.6 s
2/100
25%
Value4.6 s
71/100
10%
Value790 ms
37/100
30%
Value0
100/100
15%
Value8.8 s
36/100
10%
280 ms
378 ms
316 ms
143 ms
84 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 39% of them (34 requests) were addressed to the original Core150.com, 13% (11 requests) were made to O.twimg.com and 8% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Core150.com.
Page size can be reduced by 460.6 kB (15%)
3.1 MB
2.6 MB
In fact, the total size of Core150.com main page is 3.1 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.5 MB which makes up the majority of the site volume.
Potential reduce by 11.9 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 2.9 kB, which is 18% 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 11.9 kB or 74% of the original size.
Potential reduce by 14.1 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. Core150 images are well optimized though.
Potential reduce by 271.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 271.6 kB or 66% of the original size.
Potential reduce by 163.0 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. Core150.com needs all CSS files to be minified and compressed as it can save up to 163.0 kB or 87% of the original size.
Number of requests can be reduced by 29 (34%)
85
56
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Core150. 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 6 to 1 for CSS and as a result speed up the page load time.
core150.com
280 ms
www.core150.com
378 ms
style.css
316 ms
cbj4sku.js
143 ms
widgets.js
84 ms
path.js
197 ms
core150.js
398 ms
nav-bg.png
219 ms
logo-green-sm.png
219 ms
phone-green.png
221 ms
logo-green.png
221 ms
h-the-athletes-shaker.png
284 ms
loading.jpg
550 ms
hue-65.jpg
869 ms
hue1.jpg
962 ms
lines.png
488 ms
spinner.png
490 ms
product-attitude.jpg
547 ms
product-stackpack.jpg
602 ms
product-original.jpg
608 ms
btn-green.png
652 ms
btn-green-lg.png
700 ms
hue125.jpg
1237 ms
hue150.jpg
1206 ms
hue1-insert.jpg
935 ms
hue125-insert.jpg
964 ms
hue150-insert.jpg
1110 ms
hue-65-insert.jpg
1192 ms
hue1-sliver.png
1193 ms
33623955
132 ms
73137105
140 ms
73130966
144 ms
73129239
154 ms
56622045
149 ms
48428312
149 ms
d93e757e1104.png
34 ms
ga.js
8 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
158 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
201 ms
__utm.gif
34 ms
player.js
171 ms
player.css
146 ms
ga.js
37 ms
vuid.min.js
170 ms
like.php
282 ms
forest.png
276 ms
__utm.gif
61 ms
__utm.gif
15 ms
__utm.gif
29 ms
__utm.gif
32 ms
__utm.gif
20 ms
proxy.html
95 ms
10265583_60x60.jpg
142 ms
qeKvIRsJabD.js
178 ms
LVx-xkvaJ0b.png
194 ms
syndication
114 ms
354613994604072960
202 ms
nr-885.min.js
86 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
54 ms
689d5b4562
102 ms
proxy.jpg
47 ms
proxy.jpg
42 ms
proxy.jpg
54 ms
proxy.jpg
58 ms
proxy.jpg
51 ms
proxy.jpg
56 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
40 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
70 ms
LMxbndr9_normal.jpg
28 ms
81e4176315e26d781f5b4cca5a551832_normal.jpeg
26 ms
CdwTU9kWoAAagZD.jpg:small
27 ms
Cdv11dQWEAA34L_.jpg:small
27 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
140 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
146 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
28 ms
proxy.jpg
5 ms
proxy.jpg
5 ms
proxy.jpg
55 ms
proxy.jpg
3 ms
proxy.jpg
5 ms
jot.html
46 ms
media-instagram-image.jpg
265 ms
ig-badge-view-sprite-24.png
269 ms
btn-steppers.png
194 ms
media-video1-image.jpg
177 ms
vimeo_badge.png
200 ms
btn-video-play.png
206 ms
picture51.jpg
451 ms
core150.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.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
core150.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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
core150.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
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Core150.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Core150.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
core150.com
Open Graph description is not detected on the main page of Core150. 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: