1.7 sec in total
378 ms
1 sec
324 ms
Visit discuss.ilw.com now to see the best up-to-date Discuss ILW content for India and also check out these interesting facts you probably never knew about discuss.ilw.com
vBulletin Forums
Visit discuss.ilw.comWe analyzed Discuss.ilw.com page load time and found that the first response time was 378 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
discuss.ilw.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value2.9 s
81/100
25%
Value3.5 s
89/100
10%
Value1,020 ms
26/100
30%
Value0.041
99/100
15%
Value7.7 s
45/100
10%
378 ms
164 ms
110 ms
175 ms
285 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 72% of them (42 requests) were addressed to the original Discuss.ilw.com, 16% (9 requests) were made to Ilw.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (378 ms) belongs to the original domain Discuss.ilw.com.
Page size can be reduced by 331.3 kB (67%)
497.7 kB
166.4 kB
In fact, the total size of Discuss.ilw.com main page is 497.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 158.4 kB which makes up the majority of the site volume.
Potential reduce by 114.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. This page needs HTML code to be minified as it can gain 20.7 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 114.6 kB or 86% of the original size.
Potential reduce by 4.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. Discuss ILW images are well optimized though.
Potential reduce by 97.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 97.5 kB or 62% of the original size.
Potential reduce by 114.4 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. Discuss.ilw.com needs all CSS files to be minified and compressed as it can save up to 114.4 kB or 86% of the original size.
Number of requests can be reduced by 41 (73%)
56
15
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discuss ILW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
forumdisplay.php
378 ms
yuiloader-dom-event.js
164 ms
connection-min.js
110 ms
vbulletin-core.js
175 ms
css.php
285 ms
jquery-1.3.1.min.js
52 ms
printarticlefunctions.js
150 ms
ilw-styles.css
204 ms
vbulletin_read_marker.js
85 ms
css.php
308 ms
genfns.js
155 ms
vbulletin_md5.js
113 ms
home-flag-bkgnd.gif
45 ms
gradient-grey-down.png
49 ms
search.png
48 ms
navbit-home.png
49 ms
next-right.png
48 ms
last-right.png
47 ms
forum_old-48.png
49 ms
lastpost-right.png
66 ms
sortarrow-asc.png
65 ms
sticky.gif
73 ms
tag.png
66 ms
icon4.png
74 ms
icon1.png
75 ms
icon11.png
107 ms
icon5.png
107 ms
icon9.png
108 ms
collapse_40b.png
123 ms
thread_new-16.png
124 ms
thread-16-right.png
122 ms
thread_hot_new-16.png
138 ms
thread_hot-16.png
138 ms
thread_lock-16.png
138 ms
thread_dot-16-right.png
163 ms
logo-home.gif
46 ms
page-title-discussionboard.gif
46 ms
VIP_MENU_STRIP_AD.jpg
162 ms
google_custom_search_watermark.gif
52 ms
newbtn_middle.png
122 ms
selected-tab-gradient-with-top-alpha.png
122 ms
arrow.png
133 ms
navbit-arrow-right.png
133 ms
black_downward_arrow.png
132 ms
grey-up.png
134 ms
rss_40b.png
135 ms
thread_hot_lock-30.png
133 ms
thread_hot-30.png
162 ms
rating-trans-15_5.png
160 ms
generic_button.png
164 ms
gradient-greytowhite.png
163 ms
parse.php
104 ms
follow_button.html
24 ms
ga.js
49 ms
jot
115 ms
info.json
156 ms
btn_in_20x15.gif
104 ms
__utm.gif
18 ms
discuss.ilw.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
discuss.ilw.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
discuss.ilw.com 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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discuss.ilw.com 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 Discuss.ilw.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
discuss.ilw.com
Open Graph description is not detected on the main page of Discuss ILW. 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: