Tools & Wizards About Us
irisgem.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

irisgem.com

Irisgem Diamond: Made by you

Page Load Speed

8.1 sec in total

First Response

1.8 sec

Resources Loaded

5.5 sec

Page Rendered

817 ms

irisgem.com screenshot

About Website

Welcome to irisgem.com homepage info - get ready to check Irisgem best content right away, or after learning these important things about irisgem.com

Irisgem Diamonds are real diamonds made with the feature that makes them really special - hair, wool, and anything that is important to you! Unique as you are

Visit irisgem.com

Key Findings

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

Performance Metrics

irisgem.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

www.irisgem.com

1846 ms

style.min.css

226 ms

mediaelementplayer-legacy.min.css

224 ms

wp-mediaelement.min.css

305 ms

wc-blocks-vendors-style.css

248 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 35% of them (13 requests) were addressed to the original Irisgem.com, 46% (17 requests) were made to C0.wp.com and 14% (5 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Irisgem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.8 kB (4%)

Content Size

3.9 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Irisgem.com main page is 3.9 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 78.3 kB

  • Original 102.7 kB
  • After minification 101.1 kB
  • After compression 24.4 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.3 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 86.2 kB

  • Original 3.4 MB
  • After minification 3.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. Irisgem images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 739 B

  • Original 167.3 kB
  • After minification 167.3 kB
  • After compression 166.6 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

-1%

Potential reduce by 2.5 kB

  • Original 167.6 kB
  • After minification 167.6 kB
  • After compression 165.1 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. Irisgem.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (74%)

Requests Now

35

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.irisgem.com

www.irisgem.com

1846 ms

style.min.css

style.min.css

226 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

224 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

305 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

248 ms

wc-blocks-style.css

wc-blocks-style.css

244 ms

styles.css

styles.css

298 ms

joinchat-btn.min.css

joinchat-btn.min.css

331 ms

avia-merged-styles-956bc228e8825c5e3765bcb6b8d27099---6368defd3fe56.css

avia-merged-styles-956bc228e8825c5e3765bcb6b8d27099---6368defd3fe56.css

855 ms

post-3277.css

post-3277.css

556 ms

jetpack.css

jetpack.css

289 ms

jquery.min.js

jquery.min.js

288 ms

jquery-migrate.min.js

jquery-migrate.min.js

279 ms

s-202440.js

s-202440.js

343 ms

submit.js

submit.js

223 ms

photon.min.js

photon.min.js

217 ms

index.js

index.js

229 ms

index.js

index.js

228 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

222 ms

add-to-cart.min.js

add-to-cart.min.js

222 ms

js.cookie.min.js

js.cookie.min.js

227 ms

woocommerce.min.js

woocommerce.min.js

228 ms

cart-fragments.min.js

cart-fragments.min.js

227 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

228 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

229 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

228 ms

joinchat.min.js

joinchat.min.js

296 ms

avia-footer-scripts-e36eabc2412dc24bda4231b53a2e39e7---6368defe1b273.js

avia-footer-scripts-e36eabc2412dc24bda4231b53a2e39e7---6368defe1b273.js

709 ms

e-202440.js

e-202440.js

225 ms

LOGOirisgem-peq-1.png

LOGOirisgem-peq-1.png

769 ms

diamond-PARA-SILUETA1.png

diamond-PARA-SILUETA1.png

522 ms

Tallas-ok.png

Tallas-ok.png

654 ms

mujer001suave.png

mujer001suave.png

926 ms

box1.png

box1.png

248 ms

entypo-fontello.woff

entypo-fontello.woff

341 ms

portada-slider-3-vA.png

portada-slider-3-vA.png

494 ms

portada-slider-3-v-B.png

portada-slider-3-v-B.png

214 ms

Accessibility Review

irisgem.com accessibility score

96

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.

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

irisgem.com 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

SEO Factors

irisgem.com SEO score

79

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

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Irisgem.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Irisgem.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

irisgem.com

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