1.5 sec in total
160 ms
980 ms
347 ms
Click here to check amazing Question content for India. Otherwise, check out these important facts you probably never knew about question.com
Ask questions, get answers, help others and connect with people who have similar interests.
Visit question.comWe analyzed Question.com page load time and found that the first response time was 160 ms and then it took 1.3 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.
question.com performance score
name
value
score
weighting
Value2.1 s
79/100
10%
Value2.8 s
84/100
25%
Value4.6 s
70/100
10%
Value820 ms
35/100
30%
Value0.081
94/100
15%
Value8.7 s
36/100
10%
160 ms
83 ms
231 ms
10 ms
158 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 58% of them (40 requests) were addressed to the original Question.com, 17% (12 requests) were made to Images.intellitxt.com and 3% (2 requests) were made to Web.adblade.com. The less responsive or slowest element that took the longest time to load (246 ms) relates to the external source Images.intellitxt.com.
Page size can be reduced by 399.6 kB (61%)
657.4 kB
257.8 kB
In fact, the total size of Question.com main page is 657.4 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. 45% of websites need less resources to load. Javascripts take 547.2 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.6 kB or 77% of the original size.
Potential reduce by 598 B
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. Question images are well optimized though.
Potential reduce by 350.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 350.5 kB or 64% of the original size.
Potential reduce by 22.9 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. Question.com needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 81% of the original size.
Number of requests can be reduced by 50 (76%)
66
16
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Question. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
question.com
160 ms
www.question.com
83 ms
www.question.com
231 ms
pack-v7.css
10 ms
show.js
158 ms
pack-v3.js
48 ms
analytics.js
116 ms
gpt.js
88 ms
front.asp
143 ms
body-bg.gif
63 ms
header-bg.gif
63 ms
adv-v3.gif
81 ms
question-com-logo.png
114 ms
search-bg.png
70 ms
button-search.gif
67 ms
button-search-web.gif
66 ms
nav-bg.gif
66 ms
nav-item-bg.gif
78 ms
nav-item-bg-answer.gif
72 ms
nav-item-bg-ask.gif
70 ms
header-split-bg.gif
69 ms
boxes.png
70 ms
button-find-support-group.png
76 ms
bubble.png
86 ms
bubble-corner.gif
91 ms
magnifier.png
90 ms
18-m.png
89 ms
star_empty.png
117 ms
tick.png
110 ms
group.png
108 ms
10-m.png
109 ms
default-m.png
109 ms
29-m.png
117 ms
20-m.png
116 ms
balloon.png
171 ms
30-m.png
116 ms
26-m.png
118 ms
arrow-000-medium.png
118 ms
signin-bg-username.gif
116 ms
signin-bg-password.gif
128 ms
sign-in.gif
125 ms
users.png
128 ms
balloons.png
132 ms
post.png
130 ms
pubads_impl_81.js
69 ms
collect
30 ms
load
48 ms
impsc.php
47 ms
container.html
69 ms
jload
158 ms
itxtcss_1446206988.css
207 ms
underscore-min-ns-1.4.2.js
209 ms
core_1446569672.js
208 ms
data_1444835675.js
205 ms
debug_1395261999.js
204 ms
fx_1395261999.js
246 ms
fx2_1395261999.js
226 ms
itxt_1426253035.js
225 ms
metrics_1395261999.js
226 ms
tmpl_1443709758.js
226 ms
ui_1447845393.js
232 ms
ui_mobile_1423653241.js
245 ms
zone930.css
243 ms
quant.js
107 ms
beacon.js
103 ms
pixel;r=518225694;a=p-b8GPCpJxfqYm2;fpan=1;fpa=P0-1875077071-1456765509107;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456765509107;tzo=-180;ref=;url=https%3A%2F%2Fwww.question.com%2F;ogl=
100 ms
mon
37 ms
dt
66 ms
_common_dz.css
33 ms
question.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
Form elements do not have associated labels
Links do not have a discernible name
question.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
question.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Question.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 Question.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.
question.com
Open Graph description is not detected on the main page of Question. 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: