4.3 sec in total
190 ms
2.9 sec
1.3 sec
Welcome to tollywoo.ooo homepage info - get ready to check Tollywoo best content for India right away, or after learning these important things about tollywoo.ooo
The perfect marketplace for fans, movie enthusiasts and fashion forward youth to not just admire their favourite stars but also become one.
Visit tollywoo.oooWe analyzed Tollywoo.ooo page load time and found that the first response time was 190 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tollywoo.ooo performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value27.3 s
0/100
25%
Value18.3 s
0/100
10%
Value3,060 ms
2/100
30%
Value0.009
100/100
15%
Value31.4 s
0/100
10%
190 ms
442 ms
61 ms
58 ms
45 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tollywoo.ooo, 61% (57 requests) were made to Bollywoo.ooo and 11% (10 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Bollywoo.ooo.
Page size can be reduced by 15.5 MB (24%)
65.7 MB
50.2 MB
In fact, the total size of Tollywoo.ooo main page is 65.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. Only a small number of websites need less resources to load. Images take 64.7 MB which makes up the majority of the site volume.
Potential reduce by 417.6 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 417.6 kB or 86% of the original size.
Potential reduce by 15.0 MB
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, Tollywoo needs image optimization as it can save up to 15.0 MB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 65.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 65.1 kB or 16% of the original size.
Potential reduce by 1.6 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. Tollywoo.ooo has all CSS files already compressed.
Number of requests can be reduced by 36 (40%)
90
54
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tollywoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
tollywoo.ooo
190 ms
bollywoo.ooo
442 ms
gtm.js
61 ms
theme.js
58 ms
preloads.js
45 ms
load_feature-182c005fe54a3c232faa50c6052f25e136bfbf5dd11fcde6717a2ba8298f44a5.js
43 ms
theme.css
43 ms
shopify.css
75 ms
shopify.js
87 ms
reelup_global.js
55 ms
announcement-bar-essential-apps.js
74 ms
protector.js
156 ms
protector.css
107 ms
shopify-perf-kit-1.0.0.min.js
39 ms
reels_carousel.css
155 ms
reels_carousel.js
99 ms
section-mailing-popup.js
30 ms
product-quickshop.js
68 ms
cart.js
69 ms
vendor-video.js
84 ms
Bollywoo_logo_Register_1.png
108 ms
Bar_BW.png
106 ms
cb_banner_1.jpg
128 ms
cb_banner_4.jpg
127 ms
banner_04.jpg
129 ms
srikanth_Mobile_merchandise_banner_2.jpg
125 ms
banner_022.jpg
125 ms
mobile_04.jpg
284 ms
BM_web_banner_1.png
219 ms
BM_mobile_banner_2.png
178 ms
mockup-of-a-man-wearing-an-oversized-t-shirt-and-sunglasses-m25272_13_b96174a7-a69d-483a-8c24-b429352e022a.png
442 ms
GuruGogh-_2024_-3-2lowresB.png
170 ms
t-shirt-mockup-of-a-young-man-taking-a-selfie-in-a-kitchen-45966-r-el2_1.png
149 ms
AdsSRKstroy4.png
224 ms
OversizeFront-BackCombineWhiteT.png
554 ms
NaatuNaatuartworkCloseupwhiteT.png
282 ms
10_71021a45-033c-49bd-8fd0-12cde251c27f.png
573 ms
artwork.jpg
543 ms
round-neck-t-shirt-mockup-of-a-man-wearing-a-bucket-hat-m29307.png
549 ms
GuruDuttaPRINT-1.jpg
545 ms
DevAnandUnisexTShirtCloseupview2.png
563 ms
DevAnandCloseUpViewWhiteT.png
560 ms
OversizeFront-BackCombineBlackT.png
584 ms
NaatuNaatuartworkCloseupblackT.png
557 ms
OversizeQueenandShashiTCloseup.png
578 ms
OversizeQueenandShashiTModel2.png
760 ms
WB_Post_image_1.jpg
625 ms
Vintage_Heartbreak_black.jpg
581 ms
Actor-570x710.jpg
624 ms
Deepika-570x710_b3f9c2dc-a729-43bc-bc92-26b039549d6e.jpg
623 ms
964x1200pxThumbnail.jpg
623 ms
001_6_1.webp
623 ms
HP_WEB_BANNER_2.jpg
646 ms
HP_MOBILE_BANNER_2.jpg
642 ms
image1.png
747 ms
css2
30 ms
Untitled_design_f29607c5-f79b-40c2-9ae6-3c0be9e35bbc.jpg
624 ms
kiwi-sdk-17-prod-min.js
180 ms
zbf14pr8Mv8
118 ms
trekkie.storefront.6aa08e273db3f0f2b670a27b6e6e37eb36379a04.min.js
549 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
649 ms
shopify-boomerang-1.0.0.min.js
643 ms
Untitled_design_cf2bbbed-dab0-48fa-b2d9-d5b1dc20db8e.jpg
643 ms
back-view-mockup-of-a-man-wearing-an-oversized-t-shirt-m25216_062fd401-43eb-4717-a5fc-a8e029145a83.png
745 ms
oversized-t-shirt-mockup-featuring-a-man-with-sunglasses-m25265_cf0e9b1a-0bb5-498e-9ba8-fd30f9a76304.png
752 ms
back-view-hoodie-mockup-featuring-a-curly-haired-man-posing-against-a-pink-light-m28993.png
767 ms
long-sleeve-tee-mockup-featuring-a-bearded-man-checking-his-phone-on-the-street-31834.png
737 ms
returns.png
714 ms
black.png
1065 ms
www-player.css
9 ms
www-embed-player.js
34 ms
base.js
66 ms
white.png
966 ms
ad_status.js
220 ms
aDz_T_gaBrysQcZbaYaX8h92PYnkBHHJotKz2yKPZZ4.js
169 ms
embed.js
88 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
133 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
137 ms
id
29 ms
Create
101 ms
GenerateIT
16 ms
avada-boost-sales.min.js
92 ms
avada-fsb.min.js
95 ms
avada-sale-pops-v2.min.js
94 ms
shopify-script-glider-async.js
233 ms
qr-tracking.js
765 ms
shopify-app.js
785 ms
shopify-script-glider.js
22 ms
jquery.min.js
16 ms
ajax.php
395 ms
script.min.js
42 ms
zuck.min.css
25 ms
snapgram.min.css
28 ms
zuck.js
26 ms
tollywoo.ooo 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
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
tollywoo.ooo best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tollywoo.ooo SEO score
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 doesn't use 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 Tollywoo.ooo 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 Tollywoo.ooo 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.
tollywoo.ooo
Open Graph description is not detected on the main page of Tollywoo. 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: