Tools & Wizards About Us
treasure.com screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

treasure.com

Online Auctions For Collectors With The Most Watchers - Metal Detectors

Page Load Speed

12.9 sec in total

First Response

538 ms

Resources Loaded

9.9 sec

Page Rendered

2.5 sec

treasure.com screenshot

About Website

Click here to check amazing Treasure content. Otherwise, check out these important facts you probably never knew about treasure.com

This Ace.com page shows you the most important online auctions for Metal Detectors ranked by the number of unique people watching them.

Visit treasure.com

Key Findings

We analyzed Treasure.com page load time and found that the first response time was 538 ms and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

treasure.com performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

index.php

538 ms

ace.css

296 ms

plusone.js

296 ms

widgets.js

154 ms

in.js

187 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Treasure.com, 11% (9 requests) were made to Apis.google.com and 10% (8 requests) were made to Ace.com. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Thumbs.ebaystatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.5 kB (41%)

Content Size

763.2 kB

After Optimization

451.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Treasure.com main page is 763.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. 70% of websites need less resources to load. Javascripts take 397.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 54.9 kB

  • Original 68.9 kB
  • After minification 67.3 kB
  • After compression 14.0 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.9 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 13.5 kB

  • Original 293.7 kB
  • After minification 280.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. Treasure images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 240.4 kB

  • Original 397.1 kB
  • After minification 397.1 kB
  • After compression 156.7 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 240.4 kB or 61% of the original size.

CSS Optimization

-76%

Potential reduce by 2.7 kB

  • Original 3.5 kB
  • After minification 3.0 kB
  • After compression 820 B

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. Treasure.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.

Requests Breakdown

Number of requests can be reduced by 22 (28%)

Requests Now

79

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Treasure. 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.

Network Requests Diagram

index.php

index.php

538 ms

ace.css

ace.css

296 ms

plusone.js

plusone.js

296 ms

widgets.js

widgets.js

154 ms

in.js

in.js

187 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

175 ms

mjosAEKYzEzeuE-BIt17LNg.jpg

mjosAEKYzEzeuE-BIt17LNg.jpg

2853 ms

1

1

4186 ms

mKgnrLeCCJSqYXS_mKBShqQ.jpg

mKgnrLeCCJSqYXS_mKBShqQ.jpg

2839 ms

mDcz95zjfehQNDsNfQcwEXw.jpg

mDcz95zjfehQNDsNfQcwEXw.jpg

3347 ms

mA7zGuN6RnaUhrQB6kcKM1w.jpg

mA7zGuN6RnaUhrQB6kcKM1w.jpg

3337 ms

mK4MlNMKoafpChiKNFonxFg.jpg

mK4MlNMKoafpChiKNFonxFg.jpg

3338 ms

mMxEp-Fulyj8k5A2lo_vjBA.jpg

mMxEp-Fulyj8k5A2lo_vjBA.jpg

3337 ms

mNTS18TWqMshi3dzuKdp64g.jpg

mNTS18TWqMshi3dzuKdp64g.jpg

3337 ms

mvn7njkrlFgIdGQtpcnxBNQ.jpg

mvn7njkrlFgIdGQtpcnxBNQ.jpg

3337 ms

mc6dHUFKoQtMwMjIHuwo89g.jpg

mc6dHUFKoQtMwMjIHuwo89g.jpg

4197 ms

mbvIwpt-45r-YIqVNzeUe2g.jpg

mbvIwpt-45r-YIqVNzeUe2g.jpg

4195 ms

m1_Ph65dzxMQtN037WyebDQ.jpg

m1_Ph65dzxMQtN037WyebDQ.jpg

4195 ms

mfruLwoR_lUieEGcdzZ9dfg.jpg

mfruLwoR_lUieEGcdzZ9dfg.jpg

4166 ms

m97SG7rw8eYbYOSnBnk9gSw.jpg

m97SG7rw8eYbYOSnBnk9gSw.jpg

4166 ms

mOHFsomjWhQvmPNhizhmPsw.jpg

mOHFsomjWhQvmPNhizhmPsw.jpg

4165 ms

mX2wKnrmntO6cKDwtiVoUaA.jpg

mX2wKnrmntO6cKDwtiVoUaA.jpg

5147 ms

meh5knqXvgVzRIF3Rk2BvWQ.jpg

meh5knqXvgVzRIF3Rk2BvWQ.jpg

5148 ms

m5KfzNuKWeUY9EHD1kSr5DQ.jpg

m5KfzNuKWeUY9EHD1kSr5DQ.jpg

5146 ms

mP3zdn4iF7IxGK5uAXZMzkw.jpg

mP3zdn4iF7IxGK5uAXZMzkw.jpg

5146 ms

mzv3qa157u2QtXaxSQTSIVg.jpg

mzv3qa157u2QtXaxSQTSIVg.jpg

5147 ms

mzF_oIy5grH4eqskxaOyr5w.jpg

mzF_oIy5grH4eqskxaOyr5w.jpg

5146 ms

m8IMslcAmpDuMMxXeYDSZmA.jpg

m8IMslcAmpDuMMxXeYDSZmA.jpg

5837 ms

mt_GobCGwlFZs0jGDMohZbw.jpg

mt_GobCGwlFZs0jGDMohZbw.jpg

5837 ms

mYm-m8gfQI3QEoc280UK-qQ.jpg

mYm-m8gfQI3QEoc280UK-qQ.jpg

5770 ms

mHCbk2WZTt0HkM5Qnwk0BYQ.jpg

mHCbk2WZTt0HkM5Qnwk0BYQ.jpg

5818 ms

mF6FdpzpKtEJTvWfjbh8tjA.jpg

mF6FdpzpKtEJTvWfjbh8tjA.jpg

5817 ms

mmasyy5fz9_3Ter5YGYIkCQ.jpg

mmasyy5fz9_3Ter5YGYIkCQ.jpg

5816 ms

mSx133z5AmY4_XhIDOkV_Lg.jpg

mSx133z5AmY4_XhIDOkV_Lg.jpg

6585 ms

mtxdpgOZpyIJS8Y2ViiKyZw.jpg

mtxdpgOZpyIJS8Y2ViiKyZw.jpg

6575 ms

mrwMmddcYP_bttmm_Epugbw.jpg

mrwMmddcYP_bttmm_Epugbw.jpg

6574 ms

mPiRfygrTdrXPxzCugfTT-g.jpg

mPiRfygrTdrXPxzCugfTT-g.jpg

6604 ms

mzBOb7-uHta0eSCX_dRdYgw.jpg

mzBOb7-uHta0eSCX_dRdYgw.jpg

6573 ms

m3jZ8SiPLlZq2HKiY9WRahA.jpg

m3jZ8SiPLlZq2HKiY9WRahA.jpg

6573 ms

mDsZdbIobcFIW9RWx0FP_qA.jpg

mDsZdbIobcFIW9RWx0FP_qA.jpg

7112 ms

m4nhGpx6peMZjrph2PzaZcw.jpg

m4nhGpx6peMZjrph2PzaZcw.jpg

7665 ms

meuONsshc_vktAwXzHh6R9w.jpg

meuONsshc_vktAwXzHh6R9w.jpg

7111 ms

mCEbzWM1n3ZcJLiL7M0vY0g.jpg

mCEbzWM1n3ZcJLiL7M0vY0g.jpg

7665 ms

4Aces.jpg

4Aces.jpg

728 ms

ebay_market_144x59.gif

ebay_market_144x59.gif

1342 ms

all.js

all.js

1303 ms

ace03.jpg

ace03.jpg

1302 ms

secureAnonymousFramework

secureAnonymousFramework

2209 ms

button4.gif

button4.gif

1539 ms

button1a.gif

button1a.gif

2061 ms

down.gif

down.gif

2042 ms

3048 ms

mD8c69hEHkK7M5AG1uq7xQg.jpg

mD8c69hEHkK7M5AG1uq7xQg.jpg

4883 ms

mL4ZEnWPcXe_k9tqkE13A_Q.jpg

mL4ZEnWPcXe_k9tqkE13A_Q.jpg

4882 ms

P5DLcu0KGJB.js

P5DLcu0KGJB.js

1377 ms

P5DLcu0KGJB.js

P5DLcu0KGJB.js

2236 ms

ga.js

ga.js

1987 ms

mNFa1oNOxO9RB7MpuBoyN1w.jpg

mNFa1oNOxO9RB7MpuBoyN1w.jpg

4397 ms

mXfJfxRQ-JPavFsTP0Tor0A.jpg

mXfJfxRQ-JPavFsTP0Tor0A.jpg

4396 ms

like.php

like.php

3285 ms

quant.js

quant.js

1788 ms

button.c9025956238e7d486d74379e14f50282.js

button.c9025956238e7d486d74379e14f50282.js

2930 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

1865 ms

fastbutton

fastbutton

2309 ms

share

share

2160 ms

sprite_connect_v14.png

sprite_connect_v14.png

2273 ms

like.php

like.php

1839 ms

pixel;r=1640279178;a=p-133RSKTXVc7GQ;fpan=1;fpa=P0-1975489887-1475490603573;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1475490603573;tzo=-180;ref=;url=http%3A%2F%2Fwww.ace.com%2Findex.php%3FCategoryID%3D14955%26all%3D1%26red%3D1;ogl=

pixel;r=1640279178;a=p-133RSKTXVc7GQ;fpan=1;fpa=P0-1975489887-1475490603573;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1475490603573;tzo=-180;ref=;url=http%3A%2F%2Fwww.ace.com%2Findex.php%3FCategoryID%3D14955%26all%3D1%26red%3D1;ogl=

1152 ms

__utm.gif

__utm.gif

633 ms

postmessageRelay

postmessageRelay

1529 ms

rs=AGLTcCNT78ttKNT3ABsAArTqsjMZluuKFQ

rs=AGLTcCNT78ttKNT3ABsAArTqsjMZluuKFQ

538 ms

vqCg_VhvD6i.js

vqCg_VhvD6i.js

1527 ms

FEppCFCt76d.png

FEppCFCt76d.png

1372 ms

tweet_button.c6def25548e9590b13abaa1b3330b811.en.html

tweet_button.c6def25548e9590b13abaa1b3330b811.en.html

957 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

595 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

618 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

411 ms

4229659068-postmessagerelay.js

4229659068-postmessagerelay.js

372 ms

rpc:shindig_random.js

rpc:shindig_random.js

319 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

jot.html

jot.html

18 ms

Accessibility Review

treasure.com accessibility score

52

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

treasure.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

treasure.com SEO score

64

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Treasure.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 Treasure.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.

Social Sharing Optimization

treasure.com

Open Graph description is not detected on the main page of Treasure. 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: