Access zales.com. Zales | Your Online and Local Jewelry Store

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value3,260 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

zales.com

154 ms

www.zales.com

469 ms

mobiledirect.js

42 ms

store.css

32 ms

siteJs.js

39 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 20% of them (23 requests) were addressed to the original Zales.com, 46% (53 requests) were made to Zales.imageg.net and 4% (5 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Zales.com.

Content Size

4.4 MB

After Optimization

2.9 MB

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

HTML Optimization

-85%

Potential reduce by 125.1 kB

Original 146.7 kB
After minification 112.6 kB
After compression 21.7 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. This page needs HTML code to be minified as it can gain 34.2 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 125.1 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 68.3 kB

Original 2.5 MB
After minification 2.4 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. Zales images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 1.1 MB

Original 1.5 MB
After minification 1.4 MB
After compression 440.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 1.1 MB or 71% of the original size.

CSS Optimization

-77%

Potential reduce by 218.7 kB

Original 282.2 kB
After minification 263.0 kB
After compression 63.5 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. Zales.com needs all CSS files to be minified and compressed as it can save up to 218.7 kB or 77% of the original size.

Requests Now

112

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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.

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zales.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 Zales.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

zales.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Zales | Your Online and Local Jewelry Store

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

zales.com

www.zales.com

mobiledirect.js

store.css

siteJs.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

zales.com

www.zales.com

mobiledirect.js

store.css

siteJs.js

flashobject.js

swfobject.js

site-css.xml.min.css

Df.js

Bootstrap.js

site-head-js.xml.min.js

zalesFonts.css

jquery.cycle2.min.js

jquery.cycle2.scrollVert.min.js

jquery.cycle2.swipe.min.js

jquery.cookie.js

flexslider.css

prototype-1.7.1.js

prototype1_6_extend.js

Df.Animate.js

16481822_landing.js

resxclsa.js

emailOverlay.js

btt.js

csgather.js

site-foot-js.xml.min.js

ess.autocomplete.min.css

ess.autocomplete.min.js

jquery.flexslider.js

jquery.easing.js

jquery.mousewheel.js

z_header1_149_v2.jpg

lb

z_header1_shipToStore.gif

z_header1_3.gif

header_search.gif

megas_tae10_1.jpg

megas_tae10_2.jpg

megas_tae10_3.jpg

megas_tae10_4.jpg

megas_tae10_5.jpg

z_mega6_seiko2016.jpg

megas_VWL_7.jpg