Tools & Wizards About Us
legacyfindings.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

legacyfindings.com

Legacy Findings NYC | 18k Gold, Platinum Jewelry Findings

Page Load Speed

2.5 sec in total

First Response

169 ms

Resources Loaded

2.1 sec

Page Rendered

254 ms

legacyfindings.com screenshot

About Website

Click here to check amazing Legacy Findings content. Otherwise, check out these important facts you probably never knew about legacyfindings.com

Legacy Findings NY creates custom 18k gold and platinum jewerly findings, including clasps, ear clips, shanks, and cuff links!

Visit legacyfindings.com

Key Findings

We analyzed Legacyfindings.com page load time and found that the first response time was 169 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

legacyfindings.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value3,870 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

legacyfindings.com

169 ms

legacyfindings.com

893 ms

mkz4arb.css

142 ms

theme-bundle.head_async.js

48 ms

theme-f9187250-4954-0139-bd94-0242ac110011.css

54 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Legacyfindings.com, 33% (19 requests) were made to Cdn11.bigcommerce.com and 9% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (893 ms) belongs to the original domain Legacyfindings.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.0 kB (11%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Legacyfindings.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 487.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 78.0 kB

  • Original 102.2 kB
  • After minification 96.8 kB
  • After compression 24.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 78.0 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 5.2 kB

  • Original 468.0 kB
  • After minification 462.8 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. Legacy Findings images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 34.5 kB

  • Original 487.4 kB
  • After minification 487.2 kB
  • After compression 452.9 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.

CSS Optimization

-2%

Potential reduce by 1.4 kB

  • Original 64.7 kB
  • After minification 64.7 kB
  • After compression 63.3 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. Legacyfindings.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (42%)

Requests Now

50

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy Findings. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

legacyfindings.com

legacyfindings.com

169 ms

legacyfindings.com

legacyfindings.com

893 ms

mkz4arb.css

mkz4arb.css

142 ms

theme-bundle.head_async.js

theme-bundle.head_async.js

48 ms

theme-f9187250-4954-0139-bd94-0242ac110011.css

theme-f9187250-4954-0139-bd94-0242ac110011.css

54 ms

css

css

53 ms

signup-form-widget.min.js

signup-form-widget.min.js

52 ms

js

js

88 ms

loader.js

loader.js

71 ms

theme-bundle.main.js

theme-bundle.main.js

45 ms

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

39 ms

visitor_stencil.js

visitor_stencil.js

39 ms

p.css

p.css

20 ms

ga.js

ga.js

205 ms

legacy-logo.svg

legacy-logo.svg

198 ms

BCy9IvQW4j4

BCy9IvQW4j4

342 ms

iframe.gif

iframe.gif

316 ms

unknown.png

unknown.png

562 ms

gia.jpg

gia.jpg

514 ms

jbt-member-logo.jpg

jbt-member-logo.jpg

511 ms

index.php

index.php

266 ms

Small_flat_white_closed__88520.1605556861.jpg

Small_flat_white_closed__88520.1605556861.jpg

177 ms

Hoop_lock_installed__22946.1612467575.jpg

Hoop_lock_installed__22946.1612467575.jpg

177 ms

1001w__46495.1594404201.jpg

1001w__46495.1594404201.jpg

176 ms

5004w__22793.1436616119.1280.1280__76456.1507973015.jpg

5004w__22793.1436616119.1280.1280__76456.1507973015.jpg

302 ms

1510w__40473.1596644903.jpg

1510w__40473.1596644903.jpg

511 ms

1360w__31089.1594405725.jpg

1360w__31089.1594405725.jpg

512 ms

6006w__36800.1594406292.jpg

6006w__36800.1594406292.jpg

510 ms

1205w__55029.1594402869.jpg

1205w__55029.1594402869.jpg

625 ms

video-thumbnail.png

video-thumbnail.png

207 ms

play-btn.png

play-btn.png

230 ms

blog-bestellers.jpg

blog-bestellers.jpg

625 ms

blog-are-you-hip.jpg

blog-are-you-hip.jpg

382 ms

logo-small.svg

logo-small.svg

510 ms

jquery.js

jquery.js

196 ms

d

d

108 ms

d

d

148 ms

__utm.gif

__utm.gif

41 ms

__utm.gif

__utm.gif

37 ms

underscore-min.js

underscore-min.js

10 ms

api.js

api.js

30 ms

nobot

nobot

93 ms

recaptcha__en.js

recaptcha__en.js

47 ms

www-player.css

www-player.css

13 ms

www-embed-player.js

www-embed-player.js

72 ms

base.js

base.js

93 ms

ad_status.js

ad_status.js

158 ms

signup-form-widget.css

signup-form-widget.css

134 ms

32b883b91c0dbb4adb2a4f192f7bdca6.json

32b883b91c0dbb4adb2a4f192f7bdca6.json

237 ms

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

87 ms

embed.js

embed.js

49 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

121 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

121 ms

id

id

103 ms

Create

Create

39 ms

ctct-close-x.svg

ctct-close-x.svg

16 ms

logo-ctct-white.svg

logo-ctct-white.svg

18 ms

Accessibility Review

legacyfindings.com accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

legacyfindings.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

legacyfindings.com

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