2.5 sec in total
561 ms
1.5 sec
478 ms
Click here to check amazing Concern content. Otherwise, check out these important facts you probably never knew about concern.com
Ace.com finds the most important online auctions ranked by number of unique people watching them, and provides other buyer related services.
Visit concern.comWe analyzed Concern.com page load time and found that the first response time was 561 ms and then it took 2 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.
concern.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value2.1 s
96/100
25%
Value2.1 s
99/100
10%
Value180 ms
92/100
30%
Value0.038
100/100
15%
Value7.2 s
51/100
10%
561 ms
136 ms
60 ms
88 ms
29 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Concern.com, 11% (9 requests) were made to Apis.google.com and 9% (8 requests) were made to Ace.com. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Ace.com.
Page size can be reduced by 75.7 kB (20%)
373.2 kB
297.5 kB
In fact, the total size of Concern.com main page is 373.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 251.6 kB which makes up the majority of the site volume.
Potential reduce by 53.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. 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 53.2 kB or 80% of the original size.
Potential reduce by 13.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. Concern images are well optimized though.
Potential reduce by 6.3 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 6.3 kB or 12% of the original size.
Potential reduce by 2.7 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. Concern.com needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 76% of the original size.
Number of requests can be reduced by 25 (30%)
83
58
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Concern. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.ace.com
561 ms
ace.css
136 ms
plusone.js
60 ms
widgets.js
88 ms
in.js
29 ms
show_ads.js
5 ms
cb=gapi.loaded_0
138 ms
all.js
138 ms
secureAnonymousFramework
173 ms
ca-pub-1993952457415700.js
316 ms
zrt_lookup.html
344 ms
show_ads_impl.js
226 ms
miJDWl5u4XS5WeQQkRqWnbQ.jpg
328 ms
1
468 ms
ga.js
166 ms
quant.js
208 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
445 ms
cb=gapi.loaded_1
109 ms
fastbutton
254 ms
my0AZit-9E5s7az4V0ocI1Q.jpg
291 ms
mesyYBGCWSAMYDYw9fAsfdQ.jpg
292 ms
moF1QXuLgbFbMon8j5ngK-Q.jpg
295 ms
m4-k7vUvFZRx3dKhqBaYAxQ.jpg
306 ms
m4MFPOApT161XDVVBlI3T8A.jpg
304 ms
m4TVa1kJR7a-x9YNPhRXEjA.jpg
367 ms
mg4umC7kk7n_kkIEsdRBZPw.jpg
366 ms
mmahxIZBZwskBG4Yd2jeYBA.jpg
367 ms
mMh690p-5xZMHkUYWh6uZXw.jpg
366 ms
mKZHYcaooSYE3HIn3xIJG3w.jpg
365 ms
m3pxTGVRqIyedyxzjuQx9NA.jpg
365 ms
ms2AGRrzNlw01-RxNvdR3Xw.jpg
413 ms
mO9wvWrB7B5CPgLkhCDDimg.jpg
412 ms
m9MLtsn2HNO6iPpTCoWZz6A.jpg
410 ms
mzuLsNmNoW1XJrbtjXTO0Zg.jpg
409 ms
m81ILkw3dwc8l1STyU-QeTw.jpg
410 ms
mx7T1O-bAtm6XzQt0gPO4yg.jpg
410 ms
mNtkt_ilFsEDAQZd9yOx1Eg.jpg
434 ms
mq8-2UkWTzFPFTBWicvdMtw.jpg
435 ms
m-UCvDkZCptgH5AwSTyow9w.jpg
432 ms
mEVXfiD8xwYu96yWdWbLF1g.jpg
433 ms
mmbW4T_Hi0tsR9mCB1maJOg.jpg
429 ms
mNvlvCwQKq-qnys1boI5iAw.jpg
433 ms
mYZRFRdAU75Ft2FQ1PqbgRQ.jpg
454 ms
mbvTWcnfVH6Ve9nb4TdM-BQ.jpg
453 ms
mgLXMdjcrFuzuoLFnjxKUlQ.jpg
453 ms
mylg7u-FapAJ4x3DeQkyT3g.jpg
454 ms
mVaZlaXzwPnzVtCRbWg-85A.jpg
451 ms
mmsqPdDkeQPy_PoEHqONG1g.jpg
451 ms
miDZTgJf2ULd2rwO2fpNxxw.jpg
470 ms
mWxVlSzQUCTzrnbcMpHhhOg.jpg
470 ms
m9hrW92ceSnq21Pq2ZvWzmw.jpg
469 ms
mGZFgqxg7NkdMDaG1-weazg.jpg
470 ms
mJVz3wlh205a-5raencLe_w.jpg
470 ms
mfNmaAtF_CIi8TUx1XzH8sQ.jpg
468 ms
ace03.jpg
286 ms
4Aces.jpg
296 ms
button4.gif
285 ms
button1a.gif
283 ms
down.gif
284 ms
ebay_market_144x59.gif
281 ms
like.php
345 ms
360 ms
xd_arbiter.php
179 ms
xd_arbiter.php
278 ms
share
340 ms
sprite_connect_v14.png
330 ms
postmessageRelay
325 ms
__utm.gif
121 ms
ads
241 ms
rs=AGLTcCOyEe7xIoYbKqvJH6xA3ail6lX-YA
76 ms
pixel;r=1684716503;a=p-133RSKTXVc7GQ;fpan=1;fpa=P0-869476956-1458207126595;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458207126595;tzo=-180;ref=;url=http%3A%2F%2Fwww.ace.com%2F;ogl=
159 ms
osd.js
114 ms
mITduyW5fLckAIWCvPY0wUw.jpg
210 ms
mmVeTflO1nAgZ-gWsjYMwdw.jpg
206 ms
mCjNpM89tLIE-VXfy7is7AA.jpg
202 ms
m5nNDuAWSdWQ_24b7e-PlFw.jpg
206 ms
cb=gapi.loaded_0
95 ms
cb=gapi.loaded_1
77 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
124 ms
qeKvIRsJabD.js
91 ms
LVx-xkvaJ0b.png
87 ms
3193398744-postmessagerelay.js
57 ms
rpc:shindig_random.js
84 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
71 ms
cb=gapi.loaded_0
3 ms
concern.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.
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
concern.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
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
concern.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Concern.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 Concern.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.
concern.com
Open Graph description is not detected on the main page of Concern. 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: