1.1 sec in total
98 ms
980 ms
67 ms
Click here to check amazing Trill Tea content. Otherwise, check out these important facts you probably never knew about trilltea.com
A lifestyle tea brand for millennials by millennials. WE. ARE. CULTURE.
Visit trilltea.comWe analyzed Trilltea.com page load time and found that the first response time was 98 ms and then it took 1 sec 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.
trilltea.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value7.0 s
6/100
25%
Value6.9 s
33/100
10%
Value1,570 ms
13/100
30%
Value0.002
100/100
15%
Value14.6 s
8/100
10%
98 ms
59 ms
30 ms
33 ms
119 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Trilltea.com, 93% (150 requests) were made to Static.parastorage.com and 4% (6 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (363 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 679.6 kB (62%)
1.1 MB
418.5 kB
In fact, the total size of Trilltea.com main page is 1.1 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 63.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. 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 63.4 kB or 80% of the original size.
Potential reduce by 615.6 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 615.6 kB or 61% of the original size.
Potential reduce by 557 B
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. Trilltea.com has all CSS files already compressed.
Number of requests can be reduced by 153 (96%)
159
6
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trill Tea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 149 to 1 for JavaScripts and as a result speed up the page load time.
trilltea.com
98 ms
www.trilltea.com
59 ms
require.min.js
30 ms
main-r.min.js
33 ms
bt
119 ms
567a4f_5d2aa7e181a24abc0063e7987e90cc63_277.json.z
363 ms
567a4f_c5b1307521fec89021d5662a2da698ef_276.json.z
360 ms
ugc-viewer
75 ms
bt
173 ms
react-with-addons.min.js
20 ms
lodash.min.js
17 ms
wixCodeInit.min.js
17 ms
coreUtils.js
38 ms
coreUtils.min.js
44 ms
skins.min.js
67 ms
components.min.js
65 ms
core.min.js
65 ms
mobx.umd.min.js
59 ms
mobx-react.min.js
66 ms
TweenMax.min.js
65 ms
animations.min.js
162 ms
react-with-addons.min.js
161 ms
layout.min.js
162 ms
wixappsCore.min.js
162 ms
wixappsClassics.min.js
161 ms
container.min.js
159 ms
imageZoom.min.js
162 ms
mediaZoom.min.js
163 ms
imageZoomDisplayer.min.js
161 ms
matrixGallery.min.js
163 ms
slideShowGallery.min.js
161 ms
comboBoxInput.min.js
162 ms
dialogs.min.js
164 ms
table.min.js
163 ms
wixappsBuilder.min.js
163 ms
tpa.min.js
165 ms
dataFixer.min.js
164 ms
siteUtils.min.js
164 ms
image.min.js
167 ms
balata.min.js
165 ms
translationsUtils.min.js
165 ms
hammer.min.js
165 ms
utils.min.js
166 ms
fonts.min.js
167 ms
platformUtils-bundle.js
170 ms
loggingUtils.min.js
165 ms
imageClientApi.js
163 ms
swfobject.min.js
164 ms
santaProps.min.js
138 ms
displayer.min.js
134 ms
mousetrap.min.js
115 ms
DrawSVGPlugin.min.js
116 ms
react-dom.min.js
117 ms
ScrollToPlugin.min.js
115 ms
widgets.min.js
116 ms
react-dom-server.min.js
115 ms
imageCommon.min.js
171 ms
formCommon.min.js
170 ms
textCommon.min.js
171 ms
containerCommon.min.js
170 ms
socialCommon.min.js
171 ms
galleriesCommon.min.js
169 ms
buttonCommon.min.js
169 ms
compDesignUtils.min.js
169 ms
mediaCommon.min.js
169 ms
audioCommon.min.js
169 ms
skinExports.min.js
169 ms
compUtils.min.js
169 ms
mobileLayoutUtils.js
168 ms
pm-rpc.min.js
170 ms
tweenEngine.min.js
168 ms
multilingual.min.js
167 ms
render.min.js
168 ms
color.min.js
167 ms
zepto.min.js
169 ms
xss.min.js
167 ms
bluebird.min.js
166 ms
imageClientApi.min.js
166 ms
column.min.js
166 ms
siteBackground.min.js
167 ms
hoverBox.min.js
165 ms
mediaContainerFactory.min.js
165 ms
internalMarkings.min.js
166 ms
repeater.min.js
165 ms
zoomedImage.min.js
165 ms
menuButton.min.js
165 ms
messageView.min.js
98 ms
backgroundCommon.min.js
57 ms
bt
97 ms
css
81 ms
TweenMax.min.js
27 ms
svgShape.min.js
14 ms
adminLoginButton.min.js
12 ms
wTwitterFollow.min.js
14 ms
facebookComments.min.js
14 ms
verticalAnchorsMenu.min.js
15 ms
facebookShare.min.js
16 ms
vKShareButton.min.js
14 ms
youTubeSubscribeButton.min.js
15 ms
itunesButton.min.js
15 ms
skypeCallButton.min.js
16 ms
fileUploader.min.js
16 ms
pinItPinWidget.min.js
17 ms
popupCloseTextButton.min.js
17 ms
radioButton.min.js
17 ms
radioGroup.min.js
18 ms
documentMedia.min.js
16 ms
datePicker.min.js
29 ms
contactForm.min.js
28 ms
subscribeForm.min.js
28 ms
textArea.min.js
29 ms
loginSocialBar.min.js
28 ms
googleMap.min.js
28 ms
soundCloudWidget.min.js
30 ms
paypalButton.min.js
31 ms
imageButton.min.js
31 ms
linkBar.min.js
28 ms
spotifyPlayer.min.js
29 ms
spotifyFollow.min.js
30 ms
twitterFeed.min.js
31 ms
backToTopButton.min.js
32 ms
svgCommon.min.js
32 ms
facebookLike.min.js
32 ms
facebookLikeBox.min.js
33 ms
flickrBadgeWidget.min.js
33 ms
rssButton.min.js
30 ms
tinyMenu.min.js
29 ms
groupContainer.min.js
28 ms
wGooglePlusOne.min.js
28 ms
pinterestPinIt.min.js
29 ms
pinterestFollow.min.js
28 ms
wTwitterTweet.min.js
27 ms
audioPlayer.min.js
28 ms
loginButton.min.js
27 ms
htmlComponent.min.js
27 ms
deadComponent.min.js
28 ms
mediaPlayer.min.js
27 ms
mediaControls.min.js
26 ms
singleAudioPlayer.min.js
26 ms
quickActionBar.min.js
41 ms
boxSlideShowSlide.min.js
41 ms
stripSlideShowSlide.min.js
40 ms
page.min.js
32 ms
bgImageStrip.min.js
30 ms
popupContainer.min.js
30 ms
stripContainer.min.js
30 ms
stripColumnsContainer.min.js
30 ms
exitMobileModeButton.min.js
30 ms
tpaGalleries.min.js
30 ms
flashComponent.min.js
29 ms
stripSlideShow.min.js
28 ms
mobileActionsMenu.min.js
28 ms
verticalMenu.min.js
29 ms
disqusComments.min.js
29 ms
checkbox.min.js
29 ms
gridComponent.min.js
29 ms
languageSelector.min.js
29 ms
lodash.min.js
3 ms
languages.css
25 ms
bt
63 ms
bt
3 ms
trilltea.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
trilltea.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
trilltea.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trilltea.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Trilltea.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.
trilltea.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: