Tools & Wizards About Us
starbucks.app.link screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

starbucks.app.link

Starbucks® App for iPhone® and Android™: Starbucks Coffee Company

Page Load Speed

375 ms in total

First Response

8 ms

Resources Loaded

264 ms

Page Rendered

103 ms

starbucks.app.link screenshot

About Website

Click here to check amazing Starbucks App content for United States. Otherwise, check out these important facts you probably never knew about starbucks.app.link

Use the Starbucks® app for iPhone® or the Starbucks® app for Android™ to pay or to track the Stars and Rewards you’ve earned.

Visit starbucks.app.link

Key Findings

We analyzed Starbucks.app.link page load time and found that the first response time was 8 ms and then it took 367 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

starbucks.app.link performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.6 s

92/100

10%

Network Requests Diagram

starbucks.app.link

8 ms

mystarbucks

31 ms

UxFxErrorCss_8097D4DBB3B4874308CB3816C1762BED98637360.css

29 ms

UxFxStableCssWesternEuropean_6724ABFCA058F28804A76FD40AD14C9D7A6031D9.css

31 ms

chevron.svg

32 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Starbucks.app.link, 75% (6 requests) were made to Azurefrontdoorpages.azureedge.net and 13% (1 request) were made to Starbucks.com. The less responsive or slowest element that took the longest time to load (35 ms) relates to the external source Azurefrontdoorpages.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.7 kB (2%)

Content Size

132.8 kB

After Optimization

130.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Starbucks.app.link main page is 132.8 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 127.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 2.1 kB

  • Original 2.9 kB
  • After minification 2.6 kB
  • After compression 846 B

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 376 B, which is 13% 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 2.1 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 127.4 kB
  • After minification 127.4 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. Starbucks App images are well optimized though.

CSS Optimization

-26%

Potential reduce by 631 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 1.8 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. Starbucks.app.link needs all CSS files to be minified and compressed as it can save up to 631 B or 26% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • CSS

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

Network Requests Diagram

starbucks.app.link

starbucks.app.link

8 ms

mystarbucks

mystarbucks

31 ms

UxFxErrorCss_8097D4DBB3B4874308CB3816C1762BED98637360.css

UxFxErrorCss_8097D4DBB3B4874308CB3816C1762BED98637360.css

29 ms

UxFxStableCssWesternEuropean_6724ABFCA058F28804A76FD40AD14C9D7A6031D9.css

UxFxStableCssWesternEuropean_6724ABFCA058F28804A76FD40AD14C9D7A6031D9.css

31 ms

chevron.svg

chevron.svg

32 ms

cloud_drop.svg

cloud_drop.svg

35 ms

ErrorBackground.png

ErrorBackground.png

9 ms

latest.woff

latest.woff

16 ms

Accessibility Review

starbucks.app.link accessibility score

78

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

Document doesn't have a <title> element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

starbucks.app.link 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

SEO Factors

starbucks.app.link SEO score

58

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

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 Starbucks.app.link 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 Starbucks.app.link 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

starbucks.app.link

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