9.8 sec in total
2.1 sec
7.2 sec
418 ms
Welcome to wrogn.in homepage info - get ready to check WROGN best content for India right away, or after learning these important things about wrogn.in
Find the latest trends in men's fashion and Virat's favourites right here. Stay fashion forward with our curated selection of unique styles for every occasion.
Visit wrogn.inWe analyzed Wrogn.in page load time and found that the first response time was 2.1 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wrogn.in performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value16.1 s
0/100
25%
Value10.0 s
9/100
10%
Value2,890 ms
3/100
30%
Value0.515
15/100
15%
Value18.1 s
3/100
10%
2112 ms
224 ms
441 ms
442 ms
668 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 71% of them (58 requests) were addressed to the original Wrogn.in, 12% (10 requests) were made to Images.wrogn.in and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Wrogn.in.
Page size can be reduced by 1.1 MB (56%)
2.0 MB
890.0 kB
In fact, the total size of Wrogn.in main page is 2.0 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. 65% of websites need less resources to load. Javascripts take 897.2 kB which makes up the majority of the site volume.
Potential reduce by 49.7 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 9.4 kB, which is 16% 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 49.7 kB or 82% of the original size.
Potential reduce by 5.9 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. WROGN images are well optimized though.
Potential reduce by 641.9 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 641.9 kB or 72% of the original size.
Potential reduce by 428.3 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. Wrogn.in needs all CSS files to be minified and compressed as it can save up to 428.3 kB or 85% of the original size.
Number of requests can be reduced by 51 (71%)
72
21
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WROGN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.wrogn.in
2112 ms
owl.carousel.css
224 ms
owl.theme.css
441 ms
effects.css
442 ms
styles.css
668 ms
widgets.css
444 ms
style.css
459 ms
amscroll.css
457 ms
ajaxcart.css
661 ms
bootstrap.min.css
881 ms
font-awesome.min.css
683 ms
elegantfont.css
685 ms
megamenu.css
688 ms
accordion.css
878 ms
animate.css
889 ms
responsive.css
891 ms
rtl.css
912 ms
colorbox.css
913 ms
design_default.css
1097 ms
layout_default.css
1099 ms
custom.css
1106 ms
prototype.js
1556 ms
ccard.js
1139 ms
validation.js
1143 ms
builder.js
1321 ms
effects.js
1322 ms
dragdrop.js
1325 ms
controls.js
1367 ms
slider.js
1371 ms
js.js
1541 ms
form.js
1540 ms
menu.js
1543 ms
translate.js
1594 ms
cookies.js
1599 ms
frontend.js
1760 ms
amscroll.js
1761 ms
css
78 ms
settings.css
1761 ms
2249 ms
jquery-1.8.2.min.js
1627 ms
wow.min.js
1400 ms
bootstrap.min.js
1549 ms
bootstrap-tooltip.js
1533 ms
collapse.js
1537 ms
jquery.lib.min.js
1641 ms
css
30 ms
css
48 ms
css
54 ms
jquery.ajaxcart.min.js
1530 ms
jquery-1.11.1.min.js
1786 ms
jquery.themepunch.tools.min.js
1780 ms
jquery.themepunch.revolution.min.js
1850 ms
logo_white_1_1.png
491 ms
logo-sticky.png
896 ms
logo.png
915 ms
logo_black.png
476 ms
w1.jpg
931 ms
home-tshirt-n.jpg
712 ms
home-shirt-n.jpg
695 ms
home-jeans-n.jpg
909 ms
home-trousers-n.jpg
1143 ms
home-new-look-book-n.jpg
1371 ms
icon.png
925 ms
dummy.png
251 ms
gtm.js
56 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
165 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
53 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
53 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
95 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
95 ms
4cKlrioa77J2iqTqBgkRWg.ttf
161 ms
ElegantIcons.woff
706 ms
analytics.js
87 ms
fontawesome-webfont.woff
674 ms
collect
18 ms
collect
74 ms
opener-active.png
221 ms
opener.png
234 ms
overlay.png
235 ms
loader.gif
236 ms
coloredbg.png
383 ms
WEB-BANNER-10.jpg
1729 ms
wrogn.in 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.
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 IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
wrogn.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wrogn.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Wrogn.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 Wrogn.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.
wrogn.in
Open Graph description is not detected on the main page of WROGN. 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: