Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

gillio.com

Gillio Rare Coins, Fine Jewelry & Loan - Downtown Santa Barbara

Page Load Speed

898 ms in total

First Response

124 ms

Resources Loaded

614 ms

Page Rendered

160 ms

gillio.com screenshot

About Website

Click here to check amazing Gillio content. Otherwise, check out these important facts you probably never knew about gillio.com

Gillio Rare Coins, Fine Jewelry & Loan, family owned and operated since 1971, is Santa Barbara's oldest rare coin and precious metals buyer & seller.

Visit gillio.com

Key Findings

We analyzed Gillio.com page load time and found that the first response time was 124 ms and then it took 774 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

gillio.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

72/100

10%

Network Requests Diagram

gillio.com

124 ms

gillio.com

250 ms

flick.css

134 ms

gillio.com

56 ms

style.min.css

140 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Gillio.com, 79% (30 requests) were made to 4bf320.p3cdn2.secureserver.net and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (250 ms) belongs to the original domain Gillio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.6 kB (19%)

Content Size

180.6 kB

After Optimization

146.0 kB

In fact, the total size of Gillio.com main page is 180.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 135.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 29.6 kB

  • Original 37.4 kB
  • After minification 35.8 kB
  • After compression 7.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. 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 29.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 280 B

  • Original 135.8 kB
  • After minification 135.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. Gillio images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 4.7 kB

  • Original 7.3 kB
  • After minification 7.3 kB
  • After compression 2.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 4.7 kB or 64% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gillio. According to our analytics all requests are already optimized.

Accessibility Review

gillio.com accessibility score

89

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

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

gillio.com SEO score

100

Search Engine Optimization Advices

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

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