Tools & Wizards About Us
trove.la screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    21% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 95% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

trove.la

Trove | LA's #1 Thrift Store & Boutique Consignment Shop for Clothing, Home Goods, Accessories, and More

Page Load Speed

729 ms in total

First Response

73 ms

Resources Loaded

585 ms

Page Rendered

71 ms

trove.la screenshot

About Website

Visit trove.la now to see the best up-to-date Trove content and also check out these interesting facts you probably never knew about trove.la

Top consignment and thrift shop in Los Angeles. Our competitive prices attract customers to our tasteful and trendy products. Clothing, Accessories, Home Goods, Art, and more for all sizes and genders...

Visit trove.la

Key Findings

We analyzed Trove.la page load time and found that the first response time was 73 ms and then it took 656 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

trove.la performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value22.7 s

0/100

10%

TBT (Total Blocking Time)

Value38,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.798

5/100

15%

TTI (Time to Interactive)

Value50.5 s

0/100

10%

Network Requests Diagram

www.trove.la

73 ms

minified.js

31 ms

focus-within-polyfill.js

30 ms

polyfill.min.js

77 ms

bootstrap-features.24d4529b.bundle.min.js

74 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Trove.la, 63% (17 requests) were made to Static.parastorage.com and 26% (7 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (305 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.2 kB (58%)

Content Size

401.7 kB

After Optimization

168.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Trove.la main page is 401.7 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. 35% of websites need less resources to load. HTML takes 308.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 227.5 kB

  • Original 308.3 kB
  • After minification 306.8 kB
  • After compression 80.8 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 227.5 kB or 74% of the original size.

Image Optimization

-13%

Potential reduce by 5.7 kB

  • Original 45.6 kB
  • After minification 39.9 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. Obviously, Trove needs image optimization as it can save up to 5.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 48 B

  • Original 47.8 kB
  • After minification 47.8 kB
  • After compression 47.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 9 (43%)

Requests Now

21

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.trove.la

www.trove.la

73 ms

minified.js

minified.js

31 ms

focus-within-polyfill.js

focus-within-polyfill.js

30 ms

polyfill.min.js

polyfill.min.js

77 ms

bootstrap-features.24d4529b.bundle.min.js

bootstrap-features.24d4529b.bundle.min.js

74 ms

main.24eb524d.bundle.min.js

main.24eb524d.bundle.min.js

72 ms

lodash.min.js

lodash.min.js

27 ms

react.production.min.js

react.production.min.js

72 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

74 ms

wix-perf-measure.bundle.min.js

wix-perf-measure.bundle.min.js

69 ms

react-dom.production.min.js

react-dom.production.min.js

68 ms

imageedit_18_5870929423.png

imageedit_18_5870929423.png

222 ms

cdc2eb_a14b3dc6ef724dafa353ba22a8cd5cc9~mv2.png

cdc2eb_a14b3dc6ef724dafa353ba22a8cd5cc9~mv2.png

133 ms

48a6cc_060103e8bbdb4e02b39d2975fd7de042~mv2_d_2875_2889_s_4_2.jpg

48a6cc_060103e8bbdb4e02b39d2975fd7de042~mv2_d_2875_2889_s_4_2.jpg

119 ms

48a6cc_3b8776a4375248a5bf6cf312763a6c4b~mv2_d_2071_2082_s_2.jpg

48a6cc_3b8776a4375248a5bf6cf312763a6c4b~mv2_d_2071_2082_s_2.jpg

188 ms

48a6cc_fd2fa7e25c68448985cff8b9e931b83e~mv2_d_2967_3024_s_4_2.jpg

48a6cc_fd2fa7e25c68448985cff8b9e931b83e~mv2_d_2967_3024_s_4_2.jpg

196 ms

48a6cc_2498eb7fae734c04848e71551c022559~mv2_d_3024_3040_s_4_2.jpg

48a6cc_2498eb7fae734c04848e71551c022559~mv2_d_3024_3040_s_4_2.jpg

198 ms

FOLLOW-US-ON-INSTAGRAM.png

FOLLOW-US-ON-INSTAGRAM.png

305 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

3 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

7 ms

deprecation-en.v5.html

deprecation-en.v5.html

3 ms

bolt-performance

bolt-performance

16 ms

deprecation-style.v5.css

deprecation-style.v5.css

1 ms

right-arrow.svg

right-arrow.svg

11 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

2 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

3 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

2 ms

Accessibility Review

trove.la accessibility score

98

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

Links do not have a discernible name

Best Practices

trove.la best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

trove.la SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

trove.la

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: