1.9 sec in total
119 ms
1.5 sec
263 ms
Visit 18fire.com now to see the best up-to-date 18Fire content for India and also check out these interesting facts you probably never knew about 18fire.com
Latest Indian fashionable Long Casual Cotton Kurtis, Patialas Salwar Kameez for Women & Girls Online Shopping at 18Fire. Free Shipping. Pay On Delivery, Buy Now!
Visit 18fire.comWe analyzed 18fire.com page load time and found that the first response time was 119 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
18fire.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value35.8 s
0/100
25%
Value21.4 s
0/100
10%
Value790 ms
37/100
30%
Value1.816
0/100
15%
Value22.3 s
1/100
10%
119 ms
282 ms
74 ms
69 ms
71 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 81% of them (39 requests) were addressed to the original 18fire.com, 6% (3 requests) were made to Staticxx.facebook.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (723 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 625.6 kB (25%)
2.5 MB
1.9 MB
In fact, the total size of 18fire.com main page is 2.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. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 21.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. This page needs HTML code to be minified as it can gain 4.2 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 21.0 kB or 77% of the original size.
Potential reduce by 164.1 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. 18Fire images are well optimized though.
Potential reduce by 358.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 358.9 kB or 72% of the original size.
Potential reduce by 81.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. 18fire.com needs all CSS files to be minified and compressed as it can save up to 81.6 kB or 86% of the original size.
Number of requests can be reduced by 26 (58%)
45
19
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 18Fire. 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 from 7 to 1 for CSS and as a result speed up the page load time.
18fire.com
119 ms
www.18fire.com
282 ms
main.css
74 ms
flexslider.css
69 ms
stylesheet.css
71 ms
anylinkcssmenu.css
66 ms
extra.css
104 ms
sooperfish.css
69 ms
sooperfish-theme-large.css
100 ms
jquery-1.10.2.min.js
201 ms
jquery-migrate-1.2.1.min.js
103 ms
jquery.unobtrusive-ajax.min.js
101 ms
jquery.validate.min.js
108 ms
jquery.easing-sooper.js
136 ms
jquery.sooperfish.js
136 ms
jquery.flexslider-min.js
139 ms
anylinkcssmenu.js
137 ms
jquery.validate.unobtrusive.min.js
114 ms
jquery-ui.min.js
525 ms
commonscript.js
142 ms
jquery.raty.min.js
142 ms
analytics.js
38 ms
all.js
147 ms
top_18fire.png
37 ms
logo.jpg
37 ms
sprite.png
156 ms
arrow.jpg
35 ms
INR.png
34 ms
nv_bg.png
68 ms
save.png
67 ms
buy%20long%20kurtis%20online.jpg
367 ms
1179.JPG
167 ms
1711.JPG
324 ms
sk.JPG
322 ms
222.JPG
323 ms
Bottom.JPG
324 ms
Top.JPG
603 ms
VC.JPG
368 ms
footer_nv_li.jpg
352 ms
PartialLoading.gif
352 ms
AVGARDN_2.TTF
351 ms
collect
11 ms
210 ms
xd_arbiter.php
190 ms
xd_arbiter.php
723 ms
widget_v2.132.js
31 ms
xd_arbiter.php
78 ms
avatar_simple_visitor.png
56 ms
18fire.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
18fire.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
18fire.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 18fire.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 18fire.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.
18fire.com
Open Graph description is not detected on the main page of 18Fire. 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: