3.8 sec in total
117 ms
2.2 sec
1.4 sec
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.comWe analyzed Royalteany.com page load time and found that the first response time was 117 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
royalteany.com performance score
name
value
score
weighting
Value12.9 s
0/100
10%
Value29.6 s
0/100
25%
Value15.2 s
1/100
10%
Value2,160 ms
6/100
30%
Value0.002
100/100
15%
Value29.1 s
0/100
10%
117 ms
1033 ms
178 ms
45 ms
50 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Royalteany.com, 57% (54 requests) were made to Royalny.com and 13% (12 requests) were made to D3lp3yl1i5a3qu.cloudfront.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Royalny.com.
Page size can be reduced by 1.3 MB (27%)
4.7 MB
3.4 MB
In fact, the total size of Royalteany.com main page is 4.7 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. 85% 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 113.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 16.0 kB, which is 12% 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 113.3 kB or 81% of the original size.
Potential reduce by 8.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.
Potential reduce by 127.4 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 127.4 kB or 59% of the original size.
Potential reduce by 1.0 MB
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 needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 85% of the original size.
Number of requests can be reduced by 62 (69%)
90
28
The browser has sent 90 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 36 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
royalteany.com
117 ms
1033 ms
gtm.js
178 ms
wp-emoji-release.min.js
45 ms
extra.css
50 ms
tribe-events-pro-mini-calendar-block.min.css
91 ms
style.min.css
106 ms
wc-blocks-vendors-style.css
89 ms
wc-blocks-style.css
118 ms
woocommerce-layout.css
89 ms
woocommerce.css
129 ms
jquery-ui.structure.min.css
110 ms
jquery-ui.theme.min.css
112 ms
frontend.min.css
109 ms
theme.min.css
169 ms
dashicons.min.css
146 ms
notices.min.css
134 ms
angelleye-cc-ui.css
133 ms
angular.min.js
147 ms
jquery.min.js
134 ms
jquery-migrate.min.js
163 ms
ajax-login-script.js
163 ms
frontend.js
164 ms
js
108 ms
css
159 ms
extra.css
161 ms
jquery.blockUI.min.js
156 ms
add-to-cart.min.js
158 ms
js.cookie.min.js
158 ms
woocommerce.min.js
158 ms
cart-fragments.min.js
225 ms
core.min.js
225 ms
tabs.min.js
225 ms
accordion.min.js
225 ms
theme.js
280 ms
notices.min.js
224 ms
regenerator-runtime.min.js
235 ms
wp-polyfill.min.js
235 ms
dom-ready.min.js
234 ms
hooks.min.js
234 ms
api.js
224 ms
i18n.min.js
233 ms
a11y.min.js
211 ms
jquery.json.min.js
206 ms
analytics.js
170 ms
gravityforms.min.js
167 ms
jquery.maskedinput.min.js
164 ms
custom-quanty-fields.js
151 ms
uow1rww.css
241 ms
collect
35 ms
collect
14 ms
woocommerce-smallscreen.css
13 ms
print.css
5 ms
p.css
27 ms
linkid.js
36 ms
js
114 ms
rny_mobile-white.svg
29 ms
DSC_0142.jpg
396 ms
RNY-Coffee.png
318 ms
rny_logo_Tea_blue.png
310 ms
rny_logo_Lab_blue-470w.png
391 ms
logo-rny-white.svg
29 ms
arrow-right-blue.svg
31 ms
arrow-right-white.svg
32 ms
social-instagram.svg
33 ms
rny_logo_Parent-white.svg
33 ms
sdk.js
118 ms
gtm.js
108 ms
rough-edge-white.svg
254 ms
collect
244 ms
collect
330 ms
collect
201 ms
bf2d2858f678d744cbc440669b67ce56.jpg
281 ms
c25fd2a69dd941f28875c698b448b3ad.jpg
279 ms
57e35904bccbbad30d619de88ecaf355.jpg
339 ms
753c06dc9728d39993142e2953852c49.jpg
287 ms
217b6a4cbc0a41baae810c02ec27756c.jpg
339 ms
5dc5e13417876241fafa925ee09fd004.jpg
356 ms
DSC1745.jpg
345 ms
rough-edge-light-blue.svg
196 ms
icon-plus-white.svg
195 ms
d
246 ms
d
281 ms
wARDj0u
16 ms
TSKU000016Pic1.jpg
313 ms
sdk.js
142 ms
TSKU000279Pic1.jpg
342 ms
rough-edge-dark-blue.svg
137 ms
recaptcha__en.js
169 ms
collect
36 ms
102 ms
fallback
21 ms
fallback__ltr.css
4 ms
css
14 ms
logo_48.png
4 ms
royalteany.com accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes are not valid or misspelled
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
Form elements do not have associated labels
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
royalteany.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
royalteany.com SEO score
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 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.
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: