Access yscoffee.com. Puerto Rico Coffee Roasters

25

Performance

Renders faster than
44% of other websites
64

Accessibility

Visual factors better than
that of 29% of websites
83

Best Practices

More advanced features
available than in
55% of websites
84

SEO

Google-friendlier than
52% of websites

First Response

106 ms

Resources Loaded

3.3 sec

Page Rendered

884 ms

About Website

Click here to check amazing Ys Coffee content. Otherwise, check out these important facts you probably never knew about yscoffee.com

Largest Puerto Rico coffee online store. Home of Puerto Rico's most iconic coffee brands such as Café Yaucono, Café Alto Grande, Café Rico, Café Crema and many more.

Visit yscoffee.com

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.102

89/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

yscoffee.com

106 ms

prcoffee.com

483 ms

theme-bundle.polyfills.js

420 ms

theme-bundle.head_async.js

89 ms

css

139 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yscoffee.com, 54% (52 requests) were made to Cdn11.bigcommerce.com and 21% (20 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cdn11.bigcommerce.com.

Content Size

34.5 MB

After Optimization

33.5 MB

In fact, the total size of Yscoffee.com main page is 34.5 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. Only a small number of websites need less resources to load. Images take 34.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 376.2 kB

Original 434.5 kB
After minification 373.7 kB
After compression 58.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 60.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 376.2 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 605.5 kB

Original 34.0 MB
After minification 33.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. Ys Coffee images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 247 B

Original 106.1 kB
After minification 106.1 kB
After compression 105.9 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.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

button, link, and menuitem elements do not have accessible names.

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

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

High

Links are not crawlable

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/).

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

yscoffee.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Puerto Rico Coffee Roasters

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)