Tools & Wizards About Us
truney.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

truney.com

黃金、白銀、金幣、金條、銀幣、銀條及收藏幣買賣 | Truney 貴金屬交易中心

Page Load Speed

4.3 sec in total

First Response

406 ms

Resources Loaded

3.5 sec

Page Rendered

364 ms

truney.com screenshot

About Website

Welcome to truney.com homepage info - get ready to check Truney best content for Taiwan right away, or after learning these important things about truney.com

Truney 貴金屬交易中心為台灣最大貴金屬交易商，提供黃金、白銀、鉑金、鈀金及收藏幣買賣服務，為台灣最高品質的貴金屬投資平台

Visit truney.com

Key Findings

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

Performance Metrics

truney.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

truney.com

406 ms

www.truney.com

427 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

187 ms

css_stWmzAhBXEJfRAgWBOqrXJyon-UTR6SXC9toXisJ6LI.css

371 ms

css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css

370 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 62% of them (47 requests) were addressed to the original Truney.com, 13% (10 requests) were made to Static.xx.fbcdn.net and 5% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Truney.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 303.1 kB (18%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Truney.com main page is 1.6 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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 35.1 kB

  • Original 47.3 kB
  • After minification 43.5 kB
  • After compression 12.3 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 35.1 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 32.1 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. Truney images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 135.3 kB

  • Original 204.5 kB
  • After minification 159.7 kB
  • After compression 69.2 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 135.3 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 100.7 kB

  • Original 122.2 kB
  • After minification 121.7 kB
  • After compression 21.6 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. Truney.com needs all CSS files to be minified and compressed as it can save up to 100.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (32%)

Requests Now

71

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Truney. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

truney.com

truney.com

406 ms

www.truney.com

www.truney.com

427 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

187 ms

css_stWmzAhBXEJfRAgWBOqrXJyon-UTR6SXC9toXisJ6LI.css

css_stWmzAhBXEJfRAgWBOqrXJyon-UTR6SXC9toXisJ6LI.css

371 ms

css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css

css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css

370 ms

css_BOGx9Zxm0VNY9sEr1Pj6md9nT0t9cS849A6DRYOd_Mw.css

css_BOGx9Zxm0VNY9sEr1Pj6md9nT0t9cS849A6DRYOd_Mw.css

927 ms

respond.min.js

respond.min.js

371 ms

jquery.min.js

jquery.min.js

8 ms

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

553 ms

js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js

js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js

555 ms

js_e__g9XTSrxCKtbt2KjbXEXFug-FDUSLnOdPQFr_irZA.js

js_e__g9XTSrxCKtbt2KjbXEXFug-FDUSLnOdPQFr_irZA.js

736 ms

js_QjKtId0pmWDFPfg3vOS6eMAX_nlq5siX4D67U3Qrm4o.js

js_QjKtId0pmWDFPfg3vOS6eMAX_nlq5siX4D67U3Qrm4o.js

552 ms

js_JiKGv2yOTwZY3akchodSRET5QmTvf_GCsKNFKZArUi0.js

js_JiKGv2yOTwZY3akchodSRET5QmTvf_GCsKNFKZArUi0.js

738 ms

js_3ojyrjKJ2fMzo4QRVC2-YIlZo3PmBfgcWAlyn_CEkuE.js

js_3ojyrjKJ2fMzo4QRVC2-YIlZo3PmBfgcWAlyn_CEkuE.js

737 ms

conversion.js

conversion.js

16 ms

js_B2uv6dkjoYobfQVyuXdchgrpnnx4oM0TkP_bDVf8Qrg.js

js_B2uv6dkjoYobfQVyuXdchgrpnnx4oM0TkP_bDVf8Qrg.js

736 ms

analytics.js

analytics.js

72 ms

all.js

all.js

68 ms

fbds.js

fbds.js

68 ms

body_top_bg.gif

body_top_bg.gif

211 ms

logo.png

logo.png

211 ms

wra_btm_bg.gif

wra_btm_bg.gif

211 ms

always-together-silver-coin.jpg

always-together-silver-coin.jpg

947 ms

move.jpg

move.jpg

574 ms

waza-dynastii.jpg

waza-dynastii.jpg

1109 ms

four.gif

four.gif

1138 ms

93757_Slab.jpg

93757_Slab.jpg

431 ms

maple-leaf-cougar-1oz-silver-2012__1_.jpg

maple-leaf-cougar-1oz-silver-2012__1_.jpg

432 ms

AspuBVH83whY6FkYgLLCJAnLbQYQs2P51xqAk6NmBZUF.jpg

AspuBVH83whY6FkYgLLCJAnLbQYQs2P51xqAk6NmBZUF.jpg

581 ms

DSC_4816-1000px.jpg

DSC_4816-1000px.jpg

580 ms

95986_Slab.jpg

95986_Slab.jpg

757 ms

93754_Slab.jpg

93754_Slab.jpg

764 ms

DSC_7518-ok_2.jpg

DSC_7518-ok_2.jpg

765 ms

DSC_7533-ok_1.jpg

DSC_7533-ok_1.jpg

942 ms

1gfront.jpg

1gfront.jpg

949 ms

DSC_7527-ok_0.jpg

DSC_7527-ok_0.jpg

949 ms

2016-maple-gold.jpg

2016-maple-gold.jpg

1126 ms

ZAUFS00402_11.png

ZAUFS00402_11.png

1130 ms

monkey.jpg

monkey.jpg

1132 ms

FiveBlessings1.jpg

FiveBlessings1.jpg

1133 ms

3868-AncientMythicalCreatures-1oz-Silver-Proof-HighRelief-Reverse1.jpg

3868-AncientMythicalCreatures-1oz-Silver-Proof-HighRelief-Reverse1.jpg

1291 ms

2016-MoP-Qing-Dynasty-Silver-REV.jpg

2016-MoP-Qing-Dynasty-Silver-REV.jpg

1311 ms

sheep-12f.jpg

sheep-12f.jpg

1315 ms

dragon_0.jpg

dragon_0.jpg

1316 ms

block-1.jpg

block-1.jpg

1318 ms

2-2.jpg

2-2.jpg

1322 ms

block-3.jpg

block-3.jpg

1475 ms

block-4.jpg

block-4.jpg

1494 ms

facebook_qrcode.png

facebook_qrcode.png

1497 ms

line-codebar.png

line-codebar.png

1499 ms

email.jpg

email.jpg

1683 ms

139 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1448 ms

collect

collect

52 ms

collect

collect

126 ms

170 ms

159 ms

xd_arbiter.php

xd_arbiter.php

66 ms

xd_arbiter.php

xd_arbiter.php

83 ms

65 ms

page.php

page.php

131 ms

ga-audiences

ga-audiences

38 ms

xd_arbiter.php

xd_arbiter.php

9 ms

TWxqVHEcfFH.css

TWxqVHEcfFH.css

24 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

31 ms

t-KLv3gqZy0.js

t-KLv3gqZy0.js

58 ms

uLtKx7ldlvR.js

uLtKx7ldlvR.js

60 ms

1902843_745814742130596_512080443_n.jpg

1902843_745814742130596_512080443_n.jpg

41 ms

374045_481121501933256_1687950585_n.png

374045_481121501933256_1687950585_n.png

11 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

9 ms

CSXXCvknpgK.png

CSXXCvknpgK.png

7 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

4 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

3 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

4 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

4 ms

23 ms

Accessibility Review

truney.com accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

truney.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

truney.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Truney.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Truney.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

truney.com

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