1.6 sec in total
156 ms
892 ms
514 ms
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.comWe 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.
heyfancy.com performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value13.0 s
0/100
25%
Value9.6 s
11/100
10%
Value1,220 ms
20/100
30%
Value0.039
100/100
15%
Value13.4 s
11/100
10%
156 ms
61 ms
62 ms
70 ms
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 size can be reduced by 531.0 kB (20%)
2.6 MB
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.
Potential reduce by 75.9 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.
Potential reduce by 1.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. Hey Fancy images are well optimized though.
Potential reduce by 453.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. 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.
Potential reduce by 147 B
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.
Number of requests can be reduced by 18 (69%)
26
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.
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
extract-css-moment-js-vendor-675f9459672cf966ca51-min.en-US.js
79 ms
cldr-resource-pack-a682f7ad337741eb05d6-min.en-US.js
74 ms
common-vendors-stable-f9df4447a2af25df5875-min.en-US.js
98 ms
common-vendors-c01711dcdd70b4d98c70-min.en-US.js
108 ms
common-03afb99338cb4ae341dd-min.en-US.js
121 ms
commerce-3ffa1dbd4df6ffc86cf9-min.en-US.js
190 ms
commerce-af8809f2481c48376f6a-min.en-US.css
96 ms
user-account-core-a8b364f931f4c7c55d16-min.en-US.js
105 ms
user-account-core-e7c79916101ca5555200-min.en-US.css
106 ms
performance-efd1bb5c360dd31a4ca7-min.en-US.js
296 ms
site.css
94 ms
js
264 ms
site-bundle.js
61 ms
lazy-summaries.min.js
288 ms
fancy-logo.png
352 ms
front+page+earrings.jpg
351 ms
Engagement+Rings.jpg
401 ms
P1010173.jpeg
425 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
97 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
98 ms
play-button.png
19 ms
js
51 ms
analytics.js
69 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf
51 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSWaA.ttf
50 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf
51 ms
collect
13 ms
heyfancy.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
heyfancy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
heyfancy.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
heyfancy.com
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: