Tools & Wizards About Us
meyerjewelers.net screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

meyerjewelers.net

Meyer Jewelers - Jewelry Store, Jewelry Repair, Engagement Rings

Page Load Speed

2.7 sec in total

First Response

69 ms

Resources Loaded

1.9 sec

Page Rendered

698 ms

meyerjewelers.net screenshot

About Website

Welcome to meyerjewelers.net homepage info - get ready to check Meyer Jewelers best content right away, or after learning these important things about meyerjewelers.net

A family owned jewelry store, offering a wide variety of unique and high quality jewelry at affordable prices. We offer in store Jewelry repair and cleaning.

Visit meyerjewelers.net

Key Findings

We analyzed Meyerjewelers.net page load time and found that the first response time was 69 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

meyerjewelers.net performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value3,720 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

Network Requests Diagram

meyerjewelers.net

69 ms

rs=w:1920,m

493 ms

meyerjewelers-frame.jewelershowcase.com

334 ms

script.js

36 ms

UX.4.40.0.js

37 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Meyerjewelers.net, 56% (64 requests) were made to Meyerjewelers-frame.jewelershowcase.com and 30% (34 requests) were made to Meteor.stullercloud.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.3 kB (5%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Meyerjewelers.net main page is 2.7 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. Only a small number of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 93.4 kB

  • Original 112.7 kB
  • After minification 112.7 kB
  • After compression 19.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 93.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 1.2 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. Meyer Jewelers images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 32.5 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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

-0%

Potential reduce by 199 B

  • Original 123.6 kB
  • After minification 123.6 kB
  • After compression 123.4 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. Meyerjewelers.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (62%)

Requests Now

103

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

meyerjewelers.net

meyerjewelers.net

69 ms

rs=w:1920,m

rs=w:1920,m

493 ms

meyerjewelers-frame.jewelershowcase.com

meyerjewelers-frame.jewelershowcase.com

334 ms

script.js

script.js

36 ms

UX.4.40.0.js

UX.4.40.0.js

37 ms

script.js

script.js

42 ms

js

js

70 ms

rs=w:1920,m

rs=w:1920,m

1707 ms

scc-c2.min.js

scc-c2.min.js

6 ms

bootstrap.css

bootstrap.css

36 ms

jquery.css

jquery.css

91 ms

styles.css

styles.css

78 ms

master-retail.css

master-retail.css

56 ms

embeddediframefix.css

embeddediframefix.css

55 ms

master_top.js

master_top.js

74 ms

api.js

api.js

76 ms

runtime.e4eee167c184d726b2ea.react.bundle.js

runtime.e4eee167c184d726b2ea.react.bundle.js

125 ms

npm.react-dom.ed23d76dc5702e4b22d8.react.bundle.js

npm.react-dom.ed23d76dc5702e4b22d8.react.bundle.js

132 ms

shared.ecb38aaf2be2e4fe24dd.react.bundle.js

shared.ecb38aaf2be2e4fe24dd.react.bundle.js

122 ms

npm.core-js.f530814e19fb6da62aaf.react.bundle.js

npm.core-js.f530814e19fb6da62aaf.react.bundle.js

129 ms

npm.fortawesome.52d43fad411c35ea0f9b.react.bundle.js

npm.fortawesome.52d43fad411c35ea0f9b.react.bundle.js

125 ms

npm.lodash.5f273bd298f84fc2ab85.react.bundle.js

npm.lodash.5f273bd298f84fc2ab85.react.bundle.js

150 ms

npm.react-datepicker.7ed56e7e8a8a9af078fe.react.bundle.js

npm.react-datepicker.7ed56e7e8a8a9af078fe.react.bundle.js

181 ms

npm.apollo.56c2b17f4c6268517a04.react.bundle.js

npm.apollo.56c2b17f4c6268517a04.react.bundle.js

181 ms

npm.ajv.f377289a9627442aa3db.react.bundle.js

npm.ajv.f377289a9627442aa3db.react.bundle.js

196 ms

npm.react-select.bd30a10e62afdc2435ab.react.bundle.js

npm.react-select.bd30a10e62afdc2435ab.react.bundle.js

308 ms

npm.graphql.1c41a798f6966ab6dd16.react.bundle.js

npm.graphql.1c41a798f6966ab6dd16.react.bundle.js

270 ms

npm.zod.5beea23ede42338c00e6.react.bundle.js

npm.zod.5beea23ede42338c00e6.react.bundle.js

271 ms

npm.floating-ui.b2a97dc86415e48d5846.react.bundle.js

npm.floating-ui.b2a97dc86415e48d5846.react.bundle.js

333 ms

npm.popperjs.ca4e8695179ba976c040.react.bundle.js

npm.popperjs.ca4e8695179ba976c040.react.bundle.js

334 ms

npm.react-toastify.d00b0b7fe97755ffb2b8.react.bundle.js

npm.react-toastify.d00b0b7fe97755ffb2b8.react.bundle.js

297 ms

npm.use-gesture.e4dba8ab266f61627f5f.react.bundle.js

npm.use-gesture.e4dba8ab266f61627f5f.react.bundle.js

331 ms

npm.fluent-json-schema.322d838c8fcba2cc3521.react.bundle.js

npm.fluent-json-schema.322d838c8fcba2cc3521.react.bundle.js

342 ms

npm.uri-js.599a481957a8760d1aca.react.bundle.js

npm.uri-js.599a481957a8760d1aca.react.bundle.js

351 ms

npm.react-dropzone.8fbb31b5f0e20f706a47.react.bundle.js

npm.react-dropzone.8fbb31b5f0e20f706a47.react.bundle.js

369 ms

npm.emotion.9ed662548e06304d061f.react.bundle.js

npm.emotion.9ed662548e06304d061f.react.bundle.js

366 ms

npm.apollo-link-rest.63a80c649864db2dac4d.react.bundle.js

npm.apollo-link-rest.63a80c649864db2dac4d.react.bundle.js

354 ms

npm.apollo-utilities.82d7beadfb0c4992d427.react.bundle.js

npm.apollo-utilities.82d7beadfb0c4992d427.react.bundle.js

443 ms

npm.ajv-keywords.9c7c8afa4b47aee312da.react.bundle.js

npm.ajv-keywords.9c7c8afa4b47aee312da.react.bundle.js

399 ms

npm.resize-observer-polyfill.cb40dc3096d76f8d2146.react.bundle.js

npm.resize-observer-polyfill.cb40dc3096d76f8d2146.react.bundle.js

413 ms

npm.react-transition-group.0e16361cf1475cabb49c.react.bundle.js

npm.react-transition-group.0e16361cf1475cabb49c.react.bundle.js

391 ms

npm.history.42bbb85c948e6283178b.react.bundle.js

npm.history.42bbb85c948e6283178b.react.bundle.js

386 ms

npm.optimism.35c077533ad01ec0dca6.react.bundle.js

npm.optimism.35c077533ad01ec0dca6.react.bundle.js

598 ms

npm.file-selector.8b2042d2f3beb5a069dd.react.bundle.js

npm.file-selector.8b2042d2f3beb5a069dd.react.bundle.js

425 ms

npm.react-router.c8a406f4bfe7487aa8ea.react.bundle.js

npm.react-router.c8a406f4bfe7487aa8ea.react.bundle.js

406 ms

mpt3riz.css

mpt3riz.css

114 ms

npm.qs.de21681e0ee1aecfc4df.react.bundle.js

npm.qs.de21681e0ee1aecfc4df.react.bundle.js

413 ms

npm.regenerator-runtime.2a006f4b4f463f0991e1.react.bundle.js

npm.regenerator-runtime.2a006f4b4f463f0991e1.react.bundle.js

400 ms

npm.stylis.9afe1d604fac715fc0c1.react.bundle.js

npm.stylis.9afe1d604fac715fc0c1.react.bundle.js

385 ms

8008.f872df62e529c48e6e8e.react.bundle.js

8008.f872df62e529c48e6e8e.react.bundle.js

642 ms

react-mount.ee382f3d3da5c112eae0.react.bundle.js

react-mount.ee382f3d3da5c112eae0.react.bundle.js

560 ms

npm.core-js.350448b110e5ce41aa38.vue.bundle.js

npm.core-js.350448b110e5ce41aa38.vue.bundle.js

385 ms

dc.js

dc.js

127 ms

analytics.js

analytics.js

46 ms

gtm.js

gtm.js

87 ms

datadog-rum-v4.js

datadog-rum-v4.js

132 ms

100963546

100963546

281 ms

100963544

100963544

290 ms

100963547

100963547

403 ms

100963545

100963545

281 ms

38794951

38794951

142 ms

124351832

124351832

142 ms

124351833

124351833

522 ms

124338095

124338095

159 ms

124338096

124338096

256 ms

124338105

124338105

344 ms

124338163

124338163

294 ms

124338164

124338164

291 ms

124338165

124338165

303 ms

124338166

124338166

309 ms

124338170

124338170

307 ms

124338172

124338172

320 ms

124338174

124338174

324 ms

124340652

124340652

329 ms

124340649

124340649

420 ms

124340646

124340646

486 ms

124340645

124340645

439 ms

124340644

124340644

472 ms

15251888

15251888

420 ms

15251889

15251889

427 ms

15251890

15251890

437 ms

npm.vue.755fce23c4c2002d2880.vue.bundle.js

npm.vue.755fce23c4c2002d2880.vue.bundle.js

354 ms

npm.axios.6c7d9728616946588a34.vue.bundle.js

npm.axios.6c7d9728616946588a34.vue.bundle.js

359 ms

npm.vuex.4364f483ced94917a975.vue.bundle.js

npm.vuex.4364f483ced94917a975.vue.bundle.js

368 ms

npm.lodash.41683ec15cff5ab18434.vue.bundle.js

npm.lodash.41683ec15cff5ab18434.vue.bundle.js

378 ms

npm.popper.js.47e3261c5db10dc06b1e.vue.bundle.js

npm.popper.js.47e3261c5db10dc06b1e.vue.bundle.js

556 ms

npm.v-tooltip.2b161a5e3296d080753a.vue.bundle.js

npm.v-tooltip.2b161a5e3296d080753a.vue.bundle.js

361 ms

npm.regenerator-runtime.5ee06d49d7855e43b715.vue.bundle.js

npm.regenerator-runtime.5ee06d49d7855e43b715.vue.bundle.js

382 ms

npm.trevoreyre.e68f1dc1f0f4c4385286.vue.bundle.js

npm.trevoreyre.e68f1dc1f0f4c4385286.vue.bundle.js

557 ms

npm.qs.5e5c15b38c8cf3d1ef7a.vue.bundle.js

npm.qs.5e5c15b38c8cf3d1ef7a.vue.bundle.js

389 ms

563.4375d60ec7f686381091.vue.bundle.js

563.4375d60ec7f686381091.vue.bundle.js

411 ms

header.4f84c6d541f881076583.vue.bundle.js

header.4f84c6d541f881076583.vue.bundle.js

358 ms

knockout.js

knockout.js

1097 ms

master_bottom_with_bootstrap.js

master_bottom_with_bootstrap.js

1081 ms

67733428

67733428

34 ms

p.css

p.css

36 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

618 ms

Roboto-Regular-subset.zopfli.woff

Roboto-Regular-subset.zopfli.woff

629 ms

Roboto-Medium-subset.zopfli.woff

Roboto-Medium-subset.zopfli.woff

628 ms

Roboto-Light-subset.zopfli.woff

Roboto-Light-subset.zopfli.woff

616 ms

Roboto-Thin-subset.zopfli.woff

Roboto-Thin-subset.zopfli.woff

625 ms

Roboto-Bold-subset.zopfli.woff

Roboto-Bold-subset.zopfli.woff

624 ms

Roboto-Black-subset.zopfli.woff

Roboto-Black-subset.zopfli.woff

623 ms

124351831

124351831

619 ms

124351836

124351836

593 ms

124351999

124351999

604 ms

124352001

124352001

594 ms

124352009

124352009

596 ms

124352010

124352010

594 ms

124352011

124352011

597 ms

124351834

124351834

605 ms

d

d

23 ms

Roboto-Italic-subset.zopfli.woff

Roboto-Italic-subset.zopfli.woff

58 ms

Roboto-LightItalic-subset.zopfli.woff

Roboto-LightItalic-subset.zopfli.woff

59 ms

Accessibility Review

meyerjewelers.net accessibility score

86

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

<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

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

meyerjewelers.net best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

meyerjewelers.net SEO score

92

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

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 Meyerjewelers.net 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 Meyerjewelers.net 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

meyerjewelers.net

Open Graph data is detected on the main page of Meyer Jewelers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: