2.2 sec in total
361 ms
1.3 sec
530 ms
Visit audace.com now to see the best up-to-date Audace content for United States and also check out these interesting facts you probably never knew about audace.com
Visit audace.comWe analyzed Audace.com page load time and found that the first response time was 361 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
audace.com performance score
name
value
score
weighting
Value1.7 s
91/100
10%
Value4.6 s
35/100
25%
Value2.1 s
99/100
10%
Value120 ms
97/100
30%
Value0.035
100/100
15%
Value3.7 s
90/100
10%
361 ms
308 ms
406 ms
365 ms
402 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 87% of them (69 requests) were addressed to the original Audace.com, 4% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Cdn.signifyd.com. The less responsive or slowest element that took the longest time to load (645 ms) belongs to the original domain Audace.com.
Page size can be reduced by 311.6 kB (29%)
1.1 MB
759.7 kB
In fact, the total size of Audace.com main page is 1.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. 40% of websites need less resources to load. Images take 610.5 kB which makes up the majority of the site volume.
Potential reduce by 54.1 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 54.1 kB or 74% of the original size.
Potential reduce by 5.2 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. Audace images are well optimized though.
Potential reduce by 247.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 247.6 kB or 65% of the original size.
Potential reduce by 4.8 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. Audace.com needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 83% of the original size.
Number of requests can be reduced by 40 (52%)
77
37
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Audace. 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 as a result speed up the page load time.
audace.com
361 ms
audace.css
308 ms
audace-underwear-for-men.gif
406 ms
UN.gif
365 ms
BOM.gif
402 ms
BOX.gif
402 ms
BRI.gif
403 ms
BIU.gif
403 ms
THU.gif
405 ms
JOC.gif
403 ms
BOL.gif
404 ms
LJO.gif
404 ms
SW.gif
405 ms
SHS.gif
406 ms
SQR.gif
408 ms
BRS.gif
409 ms
BIS.gif
464 ms
THS.gif
409 ms
SP.gif
463 ms
TAS.gif
469 ms
TSP.gif
469 ms
BOD.gif
470 ms
NV.gif
468 ms
XXL.gif
480 ms
BOTTOM-END.gif
476 ms
ORANGE-CAPSULE-LEFT.gif
521 ms
ORANGE-CAPSULE-RIGHT.gif
512 ms
lg-share-en.gif
41 ms
addthis_widget.js
13 ms
jorge-snow_02.jpg
100 ms
jorge-snow_03.jpg
89 ms
jorge-snow_04.jpg
89 ms
jorge-snow_05.jpg
90 ms
gray-corner-bl.gif
533 ms
gray-corner-br.gif
513 ms
viewcartcheckout.gif
518 ms
sign-up-today.jpg
555 ms
14790.jpg
618 ms
14791.jpg
612 ms
14792.jpg
615 ms
14793.jpg
616 ms
14794.jpg
618 ms
14795.jpg
645 ms
jorge-snow_01.jpg
158 ms
signifyd-badge-dark.png
46 ms
14796.jpg
353 ms
merchant.js
28 ms
300lo.json
70 ms
14797.jpg
279 ms
16617.jpg
335 ms
19610.jpg
339 ms
19611.jpg
334 ms
19609.jpg
358 ms
17775.jpg
353 ms
19340.jpg
367 ms
14593.jpg
383 ms
transp-pixel.gif
383 ms
wet-pine-blur.jpg
464 ms
trebol.gif
404 ms
signifyd-badge-dark.png
68 ms
sh.8e5f85691f9aaa082472a194.html
58 ms
redbutton3.gif
400 ms
redbutton4.gif
421 ms
redbutton2.gif
431 ms
redbutton1.gif
434 ms
ads
224 ms
paypal-verified-seal.png
430 ms
visa22.gif
392 ms
amex22.gif
406 ms
master22.gif
419 ms
discover22.gif
425 ms
paypal46.gif
435 ms
bodymag.gif
437 ms
signup-home-arrow.gif
441 ms
facebook.gif
420 ms
twitter.gif
414 ms
dealalerts.gif
417 ms
561a10c0007c013264457a163e74bed5.gif
51 ms
ts
98 ms
audace.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.
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
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
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
audace.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
audace.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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audace.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 Audace.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.
audace.com
Open Graph description is not detected on the main page of Audace. 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: