Tools & Wizards About Us
royalteany.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

royalteany.com

Royal Tea New York: Sourcing and Blending Specialty Tea

Page Load Speed

2.2 sec in total

First Response

48 ms

Resources Loaded

1.5 sec

Page Rendered

619 ms

royalteany.com screenshot

About Website

Welcome to royalteany.com homepage info - get ready to check Royal Tea Ny best content right away, or after learning these important things about royalteany.com

Royal Tea New York sources high-quality teas from around the world and provides a transparent, affordable purchasing process.

Visit royalteany.com

Key Findings

We analyzed Royalteany.com page load time and found that the first response time was 48 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

royalteany.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

royalteany.com

48 ms

631 ms

style-point-selection-block.css

48 ms

tribe-events-pro-mini-calendar-block.min.css

40 ms

style.min.css

43 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Royalteany.com, 65% (51 requests) were made to Assets.royalny.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (631 ms) relates to the external source Royalny.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.7 kB (25%)

Content Size

541.2 kB

After Optimization

408.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalteany.com main page is 541.2 kB. 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 302.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 130.4 kB

  • Original 160.8 kB
  • After minification 143.1 kB
  • After compression 30.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 17.7 kB, which is 11% 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 130.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 21 B

  • Original 2.3 kB
  • After minification 2.3 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. Royal Tea Ny images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 302.6 kB
  • After minification 302.5 kB
  • After compression 300.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 206 B

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

Requests Breakdown

Number of requests can be reduced by 56 (86%)

Requests Now

65

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalteany.com

royalteany.com

48 ms

631 ms

style-point-selection-block.css

style-point-selection-block.css

48 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

40 ms

style.min.css

style.min.css

43 ms

woocommerce-layout.css

woocommerce-layout.css

47 ms

woocommerce.css

woocommerce.css

49 ms

wt-smart-coupon-public.css

wt-smart-coupon-public.css

49 ms

jquery-ui.structure.min.css

jquery-ui.structure.min.css

53 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

54 ms

frontend.min.css

frontend.min.css

59 ms

theme.min.css

theme.min.css

60 ms

dashicons.min.css

dashicons.min.css

57 ms

angelleye-cc-ui.css

angelleye-cc-ui.css

57 ms

jquery.min.js

jquery.min.js

58 ms

jquery-migrate.min.js

jquery-migrate.min.js

88 ms

ajax-login-script.js

ajax-login-script.js

88 ms

frontend.js

frontend.js

86 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

89 ms

add-to-cart.min.js

add-to-cart.min.js

87 ms

js.cookie.min.js

js.cookie.min.js

87 ms

woocommerce.min.js

woocommerce.min.js

87 ms

wt-smart-coupon-public.js

wt-smart-coupon-public.js

88 ms

angular.min.js

angular.min.js

89 ms

css

css

57 ms

dismissible-wp-notices.js

dismissible-wp-notices.js

85 ms

lazysizes.min.js

lazysizes.min.js

86 ms

js

js

95 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

86 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

85 ms

wp-polyfill.min.js

wp-polyfill.min.js

86 ms

hooks.min.js

hooks.min.js

87 ms

i18n.min.js

i18n.min.js

86 ms

main.js

main.js

86 ms

sourcebuster.min.js

sourcebuster.min.js

87 ms

order-attribution.min.js

order-attribution.min.js

87 ms

core.min.js

core.min.js

87 ms

tabs.min.js

tabs.min.js

88 ms

accordion.min.js

accordion.min.js

88 ms

api.js

api.js

89 ms

theme.js

theme.js

59 ms

dom-ready.min.js

dom-ready.min.js

52 ms

a11y.min.js

a11y.min.js

51 ms

jquery.json.min.js

jquery.json.min.js

51 ms

gravityforms.min.js

gravityforms.min.js

47 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

47 ms

custom-quanty-fields.js

custom-quanty-fields.js

46 ms

uow1rww.css

uow1rww.css

81 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

4 ms

print.css

print.css

3 ms

p.css

p.css

34 ms

sdk.js

sdk.js

77 ms

gtm.js

gtm.js

80 ms

rough-edge-white.svg

rough-edge-white.svg

10 ms

rough-edge-light-blue.svg

rough-edge-light-blue.svg

67 ms

icon-plus-white.svg

icon-plus-white.svg

66 ms

15528.otf

15528.otf

59 ms

d

d

58 ms

d

d

165 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

168 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

169 ms

wARDj0u

wARDj0u

14 ms

sdk.js

sdk.js

163 ms

rough-edge-dark-blue.svg

rough-edge-dark-blue.svg

109 ms

recaptcha__en.js

recaptcha__en.js

89 ms

15529.otf

15529.otf

58 ms

102 ms

15530.otf

15530.otf

39 ms

anchor

anchor

41 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

9 ms

PSKopaksc4v0TeE9MSufUBd6uLsTLN3_1JKIESb4JYg.js

PSKopaksc4v0TeE9MSufUBd6uLsTLN3_1JKIESb4JYg.js

18 ms

webworker.js

webworker.js

46 ms

logo_48.png

logo_48.png

10 ms

recaptcha__en.js

recaptcha__en.js

24 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

6 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

9 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

12 ms

Accessibility Review

royalteany.com accessibility score

98

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.

Best Practices

royalteany.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

royalteany.com SEO score

97

Search Engine Optimization Advices

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

royalteany.com

Open Graph data is detected on the main page of Royal Tea Ny. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: