1.4 sec in total
65 ms
918 ms
406 ms
Click here to check amazing Why Legend S content. Otherwise, check out these important facts you probably never knew about whylegends.com
Legends is fresh food, sports, and FUN!
Visit whylegends.comWe analyzed Whylegends.com page load time and found that the first response time was 65 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
whylegends.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value7.8 s
3/100
25%
Value10.9 s
6/100
10%
Value3,010 ms
2/100
30%
Value0.001
100/100
15%
Value18.4 s
3/100
10%
65 ms
60 ms
44 ms
56 ms
216 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Whylegends.com, 47% (14 requests) were made to Use.typekit.net and 30% (9 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (216 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 121.1 kB (4%)
2.9 MB
2.8 MB
In fact, the total size of Whylegends.com main page is 2.9 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. 55% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.9 kB or 75% of the original size.
Potential reduce by 79.3 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. Why Legend S images are well optimized though.
Number of requests can be reduced by 6 (35%)
17
11
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Legend S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.whylegends.com
65 ms
lD4sB0FniWcU7au7bpg06HCjnQxNcYXhw9VJr5OY8iJfe7tffFHN4UJLFRbh52jhWD9kZ2Z8FRqtZQsKweJDwR485AwaZ2sRFyTZiaiaO1iGpAU8Zhm0ZYw0jhNlOYiGpAU8Zhm0ZYw0jhNlOYiGpAU8Zhm0ZYw0SaBujW48Sagyjh90jhNlOfG0ihyodem1ZAoqSkoDSWmyScmDSeBRZPoRdhXK2YgkdayTdAIldcNhjPJBjhyudcCKIhZkjAonde80OAizieyTjkuuS1S7fbRKHyMMeMw6MKG4fHvgIMMjgfMfH6qJnbIbMg6eJMJ7fbKOMsMMeMS6MKG4f5w7IMMj2PMfH6qJn6IbMg6bJMJ7fbKwMsMMegI6MKG4fw9HIMIjgfMfH6qJvewbMy6IJMJ7fbRkjUMfeMS6MKG4fVsRIMJj2KMfH6qJNcwbMy6sJMJ.js
60 ms
css
44 ms
site.js
56 ms
www.whylegends.com
216 ms
common-3827d4107f55ae912a8c-min.js
48 ms
commerce-cf5ca5fa5feb9716f7f4-min.js
27 ms
commerce-7f4130fee43d9b486ac93410db2112d3-min.css
17 ms
site.css
31 ms
Background.png
20 ms
social-icons.png
16 ms
181 ms
hXjiVErvugD0IQgGeYKzpZzVJ8HVWuBXWaa5S0MUqJ6ffHhUggMdeMJ6Mk6f5Mb.woff
166 ms
lXkstp752PyVpT9RpbQQRqhH_yTu0tZu2MtGGjH5ds6ffOeUggMdeMJ6Mk6f5MS.woff
166 ms
h5lRd_EbGYU1wE3d93Z-va-ByhVVNu5ugink6nNhB6qffFc0MUMdeMJ6Mk6f5Mb.woff
167 ms
LEGENDS-Sports-Pub_MSP_01.jpg
65 ms
fresh-foods.png
25 ms
65 ms
47 ms
LEGENDS-Sports-Pub_MSP_49.jpg
48 ms
facebook.jpg
28 ms
5hF4g3NT8FfTTuG0JgCpktNrRvz2Uj5996z5KyOHdGjffHEUggMdeMJ6Mk6f5Mt.woff
45 ms
94ZebkegzRZHftxpf_ca5ipThb67sMrDBiSCgrCRPjtffOHUggMdeMJ6Mk6f5gI.woff
27 ms
xqVP_NlehvgpJO5h_V34xXezRxrbA32DzQeKgbWOwj3ffO-REN32IgCjMKM2HMJt2b.woff
29 ms
pCd-eSxohJzlFG_mee9Rq96Hk8NChPkZPrZV8D98qnjffOkREN32IgCjMKM2HMJtIM.woff
59 ms
FPSxGKpQSYNMa2DaoLxRzUPuCX7OhtO9wpajvAWtLGwffOHREN32IgCjMKM2HMJtIb.woff
73 ms
Zh5r25ARMZ8rfY1Piu1rM0PozEbdFcGLyXSqcZf6Yj6ffOAREN32IgCjMKM2HMJtM3.woff
74 ms
ypvk_yI2b-_vul5TuOuCZyV2eGRIe_yhSVroliFb0uCffOcREN32IgCjMKM2HMJtgM.woff
82 ms
sZqw0BeOokIUXxHaXeJCmT6us5b-fw1GREgUAYifXAqffO0REN32IgCjMKM2HMJtg6.woff
99 ms
iFtCRXuGomJGndf054Mx1oyo2-w8vbrtQykkKmKtBuwffOeREN32IgCjMKM2HMJtg3.woff
90 ms
whylegends.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
whylegends.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
Missing source maps for large first-party JavaScript
whylegends.com SEO score
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 Whylegends.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 Whylegends.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.
whylegends.com
Open Graph description is not detected on the main page of Why Legend S. 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: