1 sec in total
75 ms
863 ms
67 ms
Welcome to princeteahouse.com homepage info - get ready to check Prince Tea House best content right away, or after learning these important things about princeteahouse.com
Prince Tea House is an Asian-European fusion dessert, brunch, and afternoon tea spot. We’re driven to deliver comfort, friendly service, and exquisite desserts and teas. Our teas are sourced from Fran...
Visit princeteahouse.comWe analyzed Princeteahouse.com page load time and found that the first response time was 75 ms and then it took 930 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
princeteahouse.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value17.9 s
0/100
25%
Value11.2 s
5/100
10%
Value1,090 ms
24/100
30%
Value0
100/100
15%
Value16.8 s
5/100
10%
75 ms
38 ms
79 ms
274 ms
82 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Princeteahouse.com, 35% (17 requests) were made to Static.wixstatic.com and 24% (12 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (402 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 371.2 kB (47%)
787.6 kB
416.3 kB
In fact, the total size of Princeteahouse.com main page is 787.6 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. 35% of websites need less resources to load. HTML takes 453.7 kB which makes up the majority of the site volume.
Potential reduce by 361.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 361.0 kB or 80% of the original size.
Potential reduce by 7.2 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. Obviously, Prince Tea House needs image optimization as it can save up to 7.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.1 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.
Number of requests can be reduced by 14 (31%)
45
31
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prince Tea House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
www.princeteahouse.com
75 ms
minified.js
38 ms
focus-within-polyfill.js
79 ms
polyfill.min.js
274 ms
c339f800-111f-013b-a292-0cc47abd0334
82 ms
thunderbolt-commons.eb770ee8.bundle.min.js
73 ms
main.578f27a3.bundle.min.js
74 ms
lodash.min.js
72 ms
react.production.min.js
72 ms
react-dom.production.min.js
77 ms
siteTags.bundle.min.js
75 ms
wix-perf-measure.umd.min.js
77 ms
tv2track.js
137 ms
widget.js
208 ms
Prince%20tea%20house-white.png
83 ms
27eac3_499a4d4d3039486ba9baacaa16504a27~mv2.jpg
130 ms
27eac3_d973d479ab9f47b7a39d3232da56e739~mv2.gif
125 ms
final2.jpg
286 ms
DSC00368-1_edited.jpg
244 ms
5M1A9030.jpg
266 ms
6681635791251__pic_hd.jpg
340 ms
27eac3_fb257295d212476f847a09c2193ae188f000.jpg
244 ms
27eac3_5692f48ae0d845a6a59a592eb6540ed5~mv2.png
286 ms
tea-1.png
402 ms
27eac3_c7e31fed2ae9487e90fb187fca25cd1ef000.jpg
246 ms
27eac3_d43b92798ca04483b5fd53aeee599117~mv2.jpg
251 ms
Prince%20tea%20house-02.png
255 ms
27eac3_be333a747b184bdbb84003c50ec3b4d0~mv2.png
346 ms
bundle.min.js
79 ms
file.woff
154 ms
file.woff
169 ms
file.woff
185 ms
tv2track.php
42 ms
111 ms
103 ms
105 ms
103 ms
101 ms
101 ms
143 ms
137 ms
139 ms
137 ms
137 ms
widget_app_base_1709133652771.js
23 ms
deprecation-en.v5.html
5 ms
bolt-performance
25 ms
deprecation-style.v5.css
11 ms
right-arrow.svg
12 ms
princeteahouse.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
princeteahouse.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
princeteahouse.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Princeteahouse.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 Princeteahouse.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.
princeteahouse.com
Open Graph data is detected on the main page of Prince Tea House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: