Tools & Wizards About Us
diams.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

diams.com

diams : a large choice of 500,000 diamonds, jewels, pearls, meteorites / ethics and quality

Page Load Speed

6.2 sec in total

First Response

912 ms

Resources Loaded

4.7 sec

Page Rendered

588 ms

diams.com screenshot

About Website

Visit diams.com now to see the best up-to-date Diams content for Germany and also check out these interesting facts you probably never knew about diams.com

diams the largest choice in switzerland: 500,000 diamonds, at the best price.

Visit diams.com

Key Findings

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

Performance Metrics

diams.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

912 ms

calendar.min.css

102 ms

styles-m.min.css

311 ms

wallets.min.css

294 ms

blog-m.min.css

295 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 98% of them (148 requests) were addressed to the original Diams.com, 1% (1 request) were made to Static.zdassets.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (912 ms) belongs to the original domain Diams.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.5 kB (13%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 157.3 kB

  • Original 180.1 kB
  • After minification 154.2 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 25.8 kB, which is 14% 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 157.3 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 8.7 kB

  • Original 839.2 kB
  • After minification 830.5 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. Diams images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.3 kB

  • Original 228.4 kB
  • After minification 228.4 kB
  • After compression 224.1 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

-0%

Potential reduce by 214 B

  • Original 87.2 kB
  • After minification 87.2 kB
  • After compression 87.0 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. Diams.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 120 (83%)

Requests Now

145

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

912 ms

calendar.min.css

calendar.min.css

102 ms

styles-m.min.css

styles-m.min.css

311 ms

wallets.min.css

wallets.min.css

294 ms

blog-m.min.css

blog-m.min.css

295 ms

blog-new.min.css

blog-new.min.css

296 ms

style.min.css

style.min.css

299 ms

grid-mageplaza.min.css

grid-mageplaza.min.css

390 ms

font-awesome.min.css

font-awesome.min.css

393 ms

magnific-popup.min.css

magnific-popup.min.css

395 ms

styles-l.min.css

styles-l.min.css

399 ms

require.min.js

require.min.js

408 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

409 ms

mixins.min.js

mixins.min.js

487 ms

requirejs-config.min.js

requirejs-config.min.js

491 ms

snippet.js

snippet.js

36 ms

css

css

43 ms

gtm.js

gtm.js

114 ms

diams-logo.png

diams-logo.png

114 ms

champ_estival_diamant_forme.jpg

champ_estival_diamant_forme.jpg

489 ms

rtr1001_1_2.jpg

rtr1001_1_2.jpg

112 ms

bague-or-jaune-rubisajpg.jpg

bague-or-jaune-rubisajpg.jpg

114 ms

bracelet_diamant_2.00ct.jpg

bracelet_diamant_2.00ct.jpg

113 ms

bague-toi_moi_0_50ct.jpg

bague-toi_moi_0_50ct.jpg

112 ms

bo-amethyste-or-jaune_.jpg

bo-amethyste-or-jaune_.jpg

200 ms

bouton_de_manchette_meteorite_or_etoile.jpg

bouton_de_manchette_meteorite_or_etoile.jpg

201 ms

diamant-emeraude_fond-blanc.jpg

diamant-emeraude_fond-blanc.jpg

393 ms

solitaire-BN-_fond-blanc.jpg

solitaire-BN-_fond-blanc.jpg

299 ms

tennis-brac__fond-blanc.jpg

tennis-brac__fond-blanc.jpg

207 ms

perle-noire_fond-blanc.jpg

perle-noire_fond-blanc.jpg

395 ms

etoile_fond-blanc.jpg

etoile_fond-blanc.jpg

393 ms

Dimamant-Investissement_400x267px.jpg

Dimamant-Investissement_400x267px.jpg

304 ms

Expertise_400x267px.jpg

Expertise_400x267px.jpg

398 ms

Glams-diams_400x267px.jpg

Glams-diams_400x267px.jpg

405 ms

Creations_400x267px.jpg

Creations_400x267px.jpg

491 ms

jquery.min.js

jquery.min.js

592 ms

common.min.js

common.min.js

491 ms

dataPost.min.js

dataPost.min.js

494 ms

bootstrap.min.js

bootstrap.min.js

502 ms

app.min.js

app.min.js

580 ms

form-key-provider.min.js

form-key-provider.min.js

582 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

586 ms

add-webp-class-to-body.min.js

add-webp-class-to-body.min.js

597 ms

theme.min.js

theme.min.js

604 ms

opensans-400.woff

opensans-400.woff

661 ms

opensans-300.woff

opensans-300.woff

653 ms

opensans-600.woff

opensans-600.woff

662 ms

opensans-700.woff

opensans-700.woff

661 ms

Luma-Icons.woff

Luma-Icons.woff

661 ms

domReady.min.js

domReady.min.js

643 ms

mage.min.js

mage.min.js

716 ms

jquery-mixin.min.js

jquery-mixin.min.js

711 ms

Diamant_profil.png

Diamant_profil.png

747 ms

template.min.js

template.min.js

295 ms

confirm.min.js

confirm.min.js

297 ms

widget.min.js

widget.min.js

310 ms

main.min.js

main.min.js

379 ms

bootstrap.min.js

bootstrap.min.js

380 ms

types.min.js

types.min.js

300 ms

layout.min.js

layout.min.js

300 ms

text.min.js

text.min.js

315 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

368 ms

has-webp.min.js

has-webp.min.js

369 ms

wrapper.min.js

wrapper.min.js

196 ms

underscore.min.js

underscore.min.js

199 ms

translate.min.js

translate.min.js

196 ms

modal.min.js

modal.min.js

219 ms

version.min.js

version.min.js

271 ms

knockout.min.js

knockout.min.js

204 ms

knockout-es5.min.js

knockout-es5.min.js

193 ms

scripts.min.js

scripts.min.js

196 ms

main.min.js

main.min.js

208 ms

registry.min.js

registry.min.js

216 ms

engine.min.js

engine.min.js

285 ms

bootstrap.min.js

bootstrap.min.js

286 ms

observable_array.min.js

observable_array.min.js

293 ms

bound-nodes.min.js

bound-nodes.min.js

295 ms

console-logger.min.js

console-logger.min.js

297 ms

js-translation.json

js-translation.json

301 ms

modal-popup.html

modal-popup.html

263 ms

modal-slide.html

modal-slide.html

263 ms

modal-custom.html

modal-custom.html

270 ms

key-codes.min.js

key-codes.min.js

270 ms

core.min.js

core.min.js

276 ms

z-index.min.js

z-index.min.js

293 ms

validation.min.js

validation.min.js

276 ms

arrays.min.js

arrays.min.js

273 ms

compare.min.js

compare.min.js

279 ms

misc.min.js

misc.min.js

278 ms

objects.min.js

objects.min.js

286 ms

strings.min.js

strings.min.js

304 ms

template.min.js

template.min.js

368 ms

knockout-repeat.min.js

knockout-repeat.min.js

293 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

297 ms

observable_source.min.js

observable_source.min.js

297 ms

renderer.min.js

renderer.min.js

304 ms

resizable.min.js

resizable.min.js

324 ms

i18n.min.js

i18n.min.js

386 ms

scope.min.js

scope.min.js

389 ms

range.min.js

range.min.js

392 ms

mage-init.min.js

mage-init.min.js

393 ms

keyboard.min.js

keyboard.min.js

401 ms

optgroup.min.js

optgroup.min.js

423 ms

after-render.min.js

after-render.min.js

482 ms

autoselect.min.js

autoselect.min.js

484 ms

datepicker.min.js

datepicker.min.js

487 ms

outer_click.min.js

outer_click.min.js

489 ms

fadeVisible.min.js

fadeVisible.min.js

498 ms

collapsible.min.js

collapsible.min.js

520 ms

staticChecked.min.js

staticChecked.min.js

578 ms

simple-checked.min.js

simple-checked.min.js

581 ms

bind-html.min.js

bind-html.min.js

584 ms

tooltip.min.js

tooltip.min.js

586 ms

color-picker.min.js

color-picker.min.js

594 ms

events.min.js

events.min.js

604 ms

local.min.js

local.min.js

593 ms

logger.min.js

logger.min.js

594 ms

entry-factory.min.js

entry-factory.min.js

590 ms

console-output-handler.min.js

console-output-handler.min.js

592 ms

formatter.min.js

formatter.min.js

596 ms

message-pool.min.js

message-pool.min.js

605 ms

levels-pool.min.js

levels-pool.min.js

593 ms

logger-utils.min.js

logger-utils.min.js

594 ms

data.min.js

data.min.js

590 ms

disable-selection.min.js

disable-selection.min.js

594 ms

focusable.min.js

focusable.min.js

599 ms

form.min.js

form.min.js

605 ms

ie.min.js

ie.min.js

592 ms

keycode.min.js

keycode.min.js

594 ms

labels.min.js

labels.min.js

591 ms

jquery-patch.min.js

jquery-patch.min.js

594 ms

plugin.min.js

plugin.min.js

600 ms

safe-active-element.min.js

safe-active-element.min.js

606 ms

safe-blur.min.js

safe-blur.min.js

593 ms

scroll-parent.min.js

scroll-parent.min.js

594 ms

tabbable.min.js

tabbable.min.js

592 ms

unique-id.min.js

unique-id.min.js

596 ms

validation.min.js

validation.min.js

603 ms

class.min.js

class.min.js

607 ms

loader.min.js

loader.min.js

594 ms

async.min.js

async.min.js

596 ms

tooltip.html

tooltip.html

492 ms

spectrum.min.js

spectrum.min.js

490 ms

tinycolor.min.js

tinycolor.min.js

503 ms

entry.min.js

entry.min.js

439 ms

moment.min.js

moment.min.js

478 ms

jquery.validate.min.js

jquery.validate.min.js

179 ms

dom-observer.min.js

dom-observer.min.js

100 ms

bindings.min.js

bindings.min.js

102 ms

jquery.metadata.min.js

jquery.metadata.min.js

103 ms

print.min.css

print.min.css

102 ms

Accessibility Review

diams.com accessibility score

73

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

diams.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

diams.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

diams.com

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