Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 0

    Best Practices

  • 67

    SEO

    Google-friendlier than
    26% of websites

igi.org

International Gemological Institute | Jewelry & Gemstone Grading

Page Load Speed

1.2 sec in total

First Response

66 ms

Resources Loaded

1.1 sec

Page Rendered

54 ms

About Website

Visit igi.org now to see the best up-to-date Igi content for India and also check out these interesting facts you probably never knew about igi.org

IGI is the world's largest independent lab for testing & grading diamonds, gemstones, & jewelry, with 29 labs & 18 schools in 10 countries.

Visit igi.org

Key Findings

We analyzed Igi.org page load time and found that the first response time was 66 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

igi.org performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

igi.org

66 ms

igi.org

987 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Igi.org and no external sources were called. The less responsive or slowest element that took the longest time to load (987 ms) belongs to the original domain Igi.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.1 kB (2%)

Content Size

2.3 MB

After Optimization

2.3 MB

In fact, the total size of Igi.org main page is 2.3 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-12%

Potential reduce by 22 B

  • Original 177 B
  • After minification 177 B
  • After compression 155 B

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 22 B or 12% of the original size.

Image Optimization

-1%

Potential reduce by 29.3 kB

  • Original 2.1 MB
  • After minification 2.0 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. Igi images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 200.6 kB
  • After minification 200.6 kB
  • After compression 198.5 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

-9%

Potential reduce by 5.7 kB

  • Original 63.4 kB
  • After minification 63.4 kB
  • After compression 57.7 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. Igi.org has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

igi.org accessibility score

64

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

SEO Factors

igi.org SEO score

67

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igi.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Igi.org main page’s claimed encoding is . 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

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