Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

heyfancy.com

Fancy

Page Load Speed

1.6 sec in total

First Response

156 ms

Resources Loaded

892 ms

Page Rendered

514 ms

heyfancy.com screenshot

About Website

Visit heyfancy.com now to see the best up-to-date Hey Fancy content and also check out these interesting facts you probably never knew about heyfancy.com

Jewelry and objects made by independent artists and designers. Located in downtown Seattle.

Visit heyfancy.com

Key Findings

We analyzed Heyfancy.com page load time and found that the first response time was 156 ms and then it took 1.4 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

heyfancy.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

www.heyfancy.com

156 ms

css2

61 ms

legacy.js

62 ms

modern.js

70 ms

extract-css-runtime-3648d017b24c8f31d71c-min.en-US.js

69 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Heyfancy.com, 42% (14 requests) were made to Assets.squarespace.com and 18% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (425 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.0 kB (20%)

Content Size

2.6 MB

After Optimization

2.1 MB

In fact, the total size of Heyfancy.com main page is 2.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 75.9 kB

  • Original 92.3 kB
  • After minification 79.4 kB
  • After compression 16.3 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 12.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 75.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 1.5 kB

  • Original 634.2 kB
  • After minification 632.8 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. Hey Fancy images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 453.5 kB

  • Original 1.9 MB
  • After minification 1.9 MB
  • After compression 1.4 MB

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 453.5 kB or 24% of the original size.

CSS Optimization

-2%

Potential reduce by 147 B

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

Requests Breakdown

Number of requests can be reduced by 18 (69%)

Requests Now

26

After Optimization

8

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

Accessibility Review

heyfancy.com accessibility score

87

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

heyfancy.com SEO score

84

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

High

Tap targets are not sized appropriately

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 Heyfancy.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 Heyfancy.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 Hey Fancy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: