Tools & Wizards About Us
garble.in screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

garble.in

Online T-Shirts | Buy T-Shirts Online In India | Garble

Page Load Speed

11.8 sec in total

First Response

1.3 sec

Resources Loaded

10.1 sec

Page Rendered

336 ms

garble.in screenshot

About Website

Welcome to garble.in homepage info - get ready to check Garble best content for India right away, or after learning these important things about garble.in

Buy Online T- Shirt in India from wide range of stylish collection at affordable price. Check Naruto T-shirts price in India and shop online. For more information, visit at www.garble.in.

Visit garble.in

Key Findings

We analyzed Garble.in page load time and found that the first response time was 1.3 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

garble.in performance score

0

Network Requests Diagram

garble.in

1278 ms

bootstrap.css

503 ms

bootstrap-theme.css

511 ms

font-awesome.css

514 ms

font-awesome.min.css

516 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 73% of them (74 requests) were addressed to the original Garble.in, 15% (15 requests) were made to Static.xx.fbcdn.net and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Garble.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (33%)

Content Size

4.5 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Garble.in main page is 4.5 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. 75% 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 41.7 kB

  • Original 51.3 kB
  • After minification 46.0 kB
  • After compression 9.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 41.7 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 127.8 kB

  • Original 2.8 MB
  • After minification 2.7 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. Garble images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 991.7 kB

  • Original 1.3 MB
  • After minification 883.4 kB
  • After compression 259.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 991.7 kB or 79% of the original size.

CSS Optimization

-84%

Potential reduce by 317.3 kB

  • Original 376.5 kB
  • After minification 311.2 kB
  • After compression 59.2 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. Garble.in needs all CSS files to be minified and compressed as it can save up to 317.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (57%)

Requests Now

95

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

garble.in

garble.in

1278 ms

bootstrap.css

bootstrap.css

503 ms

bootstrap-theme.css

bootstrap-theme.css

511 ms

font-awesome.css

font-awesome.css

514 ms

font-awesome.min.css

font-awesome.min.css

516 ms

styles.css

styles.css

788 ms

widgets.css

widgets.css

528 ms

jquery.fancybox.css

jquery.fancybox.css

759 ms

ajax_cart_super.css

ajax_cart_super.css

755 ms

custommenu.css

custommenu.css

768 ms

jquery-ui.css

jquery-ui.css

775 ms

ma.banner7.css

ma.banner7.css

803 ms

jquery.bxslider.css

jquery.bxslider.css

1012 ms

prototype.js

prototype.js

1262 ms

ccard.js

ccard.js

1023 ms

validation.js

validation.js

1034 ms

builder.js

builder.js

1052 ms

effects.js

effects.js

1064 ms

dragdrop.js

dragdrop.js

1286 ms

controls.js

controls.js

1288 ms

slider.js

slider.js

1294 ms

js.js

js.js

1317 ms

form.js

form.js

1333 ms

menu.js

menu.js

1510 ms

translate.js

translate.js

1515 ms

cookies.js

cookies.js

1531 ms

ma.jq.slide.js

ma.jq.slide.js

1814 ms

jquery-ui.js

jquery-ui.js

2368 ms

bootstrap.js

bootstrap.js

1613 ms

bootstrap-tooltip.js

bootstrap-tooltip.js

1763 ms

ma.mobilemenu.js

ma.mobilemenu.js

1772 ms

backtotop.js

backtotop.js

1791 ms

ajax_cart_super.js

ajax_cart_super.js

1886 ms

jquery.fancybox.js

jquery.fancybox.js

2017 ms

custommenu.js

custommenu.js

2027 ms

colorpicker.js

colorpicker.js

2047 ms

jquery.cookie.js

jquery.cookie.js

1841 ms

ma.bxslider.min.js

ma.bxslider.min.js

1652 ms

ma.flexslider.js

ma.flexslider.js

1769 ms

ma.nivo.js

ma.nivo.js

1776 ms

jquery.bxslider.js

jquery.bxslider.js

1801 ms

ga.js

ga.js

9 ms

analytics.js

analytics.js

10 ms

bg_toplink.png

bg_toplink.png

254 ms

logosinglduocs.png

logosinglduocs.png

523 ms

Online_T-Shirts.jpg

Online_T-Shirts.jpg

3259 ms

Banner_5.jpg

Banner_5.jpg

3668 ms

Goku.png

Goku.png

2963 ms

a1.jpg

a1.jpg

1313 ms

4k.jpg

4k.jpg

1240 ms

3.jpg

3.jpg

2059 ms

2.jpg

2.jpg

1984 ms

bx_loader.gif

bx_loader.gif

1580 ms

footerlogo.png

footerlogo.png

1844 ms

loader.gif

loader.gif

2109 ms

__utm.gif

__utm.gif

14 ms

collect

collect

47 ms

icon-cart.png

icon-cart.png

2198 ms

collect

collect

58 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2532 ms

icon-home.png

icon-home.png

2329 ms

segoeui.woff

segoeui.woff

3180 ms

loader.gif

loader.gif

2597 ms

sdk.js

sdk.js

268 ms

icon_active.png

icon_active.png

2772 ms

3864 ms

collect

collect

24 ms

link-footer.png

link-footer.png

3017 ms

bg-footer.png

bg-footer.png

3130 ms

back-top.png

back-top.png

3278 ms

seguisb.woff

seguisb.woff

3902 ms

segoeuib.woff

segoeuib.woff

4132 ms

52 ms

xd_arbiter.php

xd_arbiter.php

220 ms

xd_arbiter.php

xd_arbiter.php

432 ms

gbla05tw-_2.png

gbla05tw-_2.png

772 ms

gbla09tw-_2.png

gbla09tw-_2.png

511 ms

gbla15tz-_2.png

gbla15tz-_2.png

272 ms

gbla16tz-_2.png

gbla16tz-_2.png

255 ms

gbla17tz-_2.png

gbla17tz-_2.png

786 ms

gbla19tw-_2.png

gbla19tw-_2.png

489 ms

btn-slider.png

btn-slider.png

511 ms

print.css

print.css

255 ms

arrows.png

arrows.png

256 ms

page.php

page.php

122 ms

Ezryo55Cca5.css

Ezryo55Cca5.css

284 ms

2NJaWBZ8ldv.css

2NJaWBZ8ldv.css

357 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

491 ms

YvxwM8R7ol8.js

YvxwM8R7ol8.js

628 ms

ihptErjAmMX.js

ihptErjAmMX.js

557 ms

1BQnIVjTFoC.js

1BQnIVjTFoC.js

624 ms

6PDLJFN-l6_.js

6PDLJFN-l6_.js

626 ms

cUsKAwzqrQw.js

cUsKAwzqrQw.js

654 ms

1907516_953313704687743_7403700600961465538_n.jpg

1907516_953313704687743_7403700600961465538_n.jpg

647 ms

983596_609543339064783_1226818324_n.png

983596_609543339064783_1226818324_n.png

717 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

86 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

85 ms

6GqoI2ZyIrf.png

6GqoI2ZyIrf.png

69 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

71 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

72 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

73 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

74 ms

SEO Factors

garble.in SEO score

0

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 Garble.in 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 Garble.in 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

garble.in

Open Graph description is not detected on the main page of Garble. 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: