Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

keepcup.com

KeepCup | Reusable Coffee Cups

Page Load Speed

9.5 sec in total

First Response

405 ms

Resources Loaded

8.2 sec

Page Rendered

860 ms

keepcup.com screenshot

About Website

Visit keepcup.com now to see the best up-to-date Keep Cup content for Australia and also check out these interesting facts you probably never knew about keepcup.com

The world's first barista standard reusable coffee cup, designed for drinking pleasure since 2009. Wholesale, design your own or customise for your brand.

Visit keepcup.com

Key Findings

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

Performance Metrics

keepcup.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value30.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,120 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value59.9 s

0/100

10%

Network Requests Diagram

keepcup.com

405 ms

store.keepcup.com

1787 ms

us.keepcup.com

1663 ms

b3625d559230311f8f06a1af3cb90549-4-SSL-1504604276.css

183 ms

bcc6a9ab94db1c40fcad89b2980b91c3-4-SSL-1504604277.css

192 ms

Our browser made a total of 170 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Keepcup.com, 74% (126 requests) were made to Keepcupcnd.scdn4.secure.raxcdn.com and 12% (20 requests) were made to Us.keepcup.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Store.keepcup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (40%)

Content Size

4.8 MB

After Optimization

2.9 MB

In fact, the total size of Keepcup.com main page is 4.8 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. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 179.4 kB

  • Original 200.8 kB
  • After minification 134.8 kB
  • After compression 21.4 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 66.0 kB, which is 33% 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 179.4 kB or 89% of the original size.

Image Optimization

-13%

Potential reduce by 348.8 kB

  • Original 2.8 MB
  • After minification 2.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. Obviously, Keep Cup needs image optimization as it can save up to 348.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 905.9 kB

  • Original 1.2 MB
  • After minification 981.3 kB
  • After compression 339.2 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 905.9 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 513.9 kB

  • Original 632.5 kB
  • After minification 615.9 kB
  • After compression 118.6 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. Keepcup.com needs all CSS files to be minified and compressed as it can save up to 513.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (38%)

Requests Now

157

After Optimization

98

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

Accessibility Review

keepcup.com accessibility score

70

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

ARIA IDs are not unique

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

High

Some elements have a [tabindex] value greater than 0

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

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

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

keepcup.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

keepcup.com SEO score

93

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

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 Keepcup.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 Keepcup.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 description is not detected on the main page of Keep Cup. 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: