1.7 sec in total
67 ms
1.4 sec
192 ms
Welcome to ex.inquirer.net homepage info - get ready to check EX Inquirer best content for Philippines right away, or after learning these important things about ex.inquirer.net
Inquirer Exchange
Visit ex.inquirer.netWe analyzed Ex.inquirer.net page load time and found that the first response time was 67 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
ex.inquirer.net performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value11.3 s
0/100
25%
Value8.9 s
15/100
10%
Value300 ms
78/100
30%
Value0.001
100/100
15%
Value10.3 s
24/100
10%
67 ms
6 ms
7 ms
8 ms
8 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 42% of them (40 requests) were addressed to the original Ex.inquirer.net, 18% (17 requests) were made to S0.2mdn.net and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (764 ms) belongs to the original domain Ex.inquirer.net.
Page size can be reduced by 455.3 kB (31%)
1.5 MB
1.0 MB
In fact, the total size of Ex.inquirer.net main page is 1.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. 65% of websites need less resources to load. Images take 869.2 kB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.0 kB or 76% of the original size.
Potential reduce by 76.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. EX Inquirer images are well optimized though.
Potential reduce by 330.2 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 330.2 kB or 60% of the original size.
Potential reduce by 22.0 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. Ex.inquirer.net needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 76% of the original size.
Number of requests can be reduced by 54 (61%)
89
35
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EX Inquirer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ex.inquirer.net
67 ms
style.css
6 ms
inquirerex.css
7 ms
globalnav.css
8 ms
dropserv2.css
8 ms
jquery.fancybox-1.3.7.min.css
22 ms
simple-pull-quote.css
7 ms
panopress.js
71 ms
panopress.css
22 ms
quant.js
24 ms
synd.js
26 ms
ex_home.css
26 ms
globalnav.css
26 ms
dropserv2.css
21 ms
show_ads.js
24 ms
jquery.js
21 ms
jquery-migrate.min.js
22 ms
jquery.fancybox-1.3.7.min.js
25 ms
jquery.easing.pack.js
24 ms
jquery.mousewheel.min.js
23 ms
wp-emoji-release.min.js
9 ms
pixel;r=608951741;a=p-08Qtd2RDpGhpY;fpan=1;fpa=P0-209334532-1456838432071;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456838432071;tzo=-180;ref=;url=http%3A%2F%2Fex.inquirer.net%2F;ogl=title.InquirerEx%2Ctype.website%2Curl.http%3A%2F%2Fex%252Einquirer%252Enet%2Cimage.http%3A%2F%2Fex%252Einquirer%252Enet%2Fwp-content%2Fthemes%2FEX_theme%2Fimages%2Finqex-landing-page_04%252Ej%2Csite_name.Inquirer%20EX%2Cdescription.Inquirer%252Enet%20Exchange%252E%20Happy%20stuff%20only%252E%20An%20official%20Inquirer%20Group%20channel%252E%20For%2Clocale.en_US%2Ctype.website%2Ctitle.INQUIRER%20EX%20-%20Inquirer%20Exchange%2Cdescription.Inquirer%20Exchange%2Curl.http%3A%2F%2Fex%252Einquirer%252Enet%2Csite_name.INQUIRER%20EX
13 ms
beacon.js
6 ms
inquirerex_bg.jpg
19 ms
masthead_gear.jpg
3 ms
fb_icon.jpg
4 ms
twitter_icon.jpg
3 ms
rss_icon.jpg
10 ms
makehomebtn.jpg
4 ms
img_home.png
7 ms
ex_logo_new.png
104 ms
ex_img_feat.jpg
10 ms
img_music.png
187 ms
img_movies.png
11 ms
img_promos.png
251 ms
img_comingsoon.png
14 ms
img_adv_exhm.jpg
19 ms
atrk.js
153 ms
analytics.js
32 ms
sdk.js
25 ms
vrs.js
28 ms
ga.js
105 ms
masthead_bg.jpg
16 ms
masthead_inqhome2.jpg
18 ms
masthead_gear.jpg
18 ms
bg_home.jpg
275 ms
ex_inf_bg.png
275 ms
ca-pub-1176084736693794.js
195 ms
zrt_lookup.html
206 ms
show_ads_impl.js
92 ms
229 ms
764 ms
229 ms
vrt.outbrain.com
158 ms
vrp.outbrain.com
157 ms
collect
126 ms
145 ms
ads
340 ms
xd_arbiter.php
77 ms
xd_arbiter.php
109 ms
expansion_embed.js
99 ms
atrk.gif
101 ms
collect
106 ms
osd.js
48 ms
ads
199 ms
collect
80 ms
test.png
113 ms
ga-audiences
31 ms
ga-audiences
26 ms
000000_new_ico.gif
27 ms
abg.js
27 ms
express_html_inpage_rendering_lib_200_120.js
29 ms
dvtp_src.js
39 ms
lidar.js
12 ms
index.html
13 ms
TweenLite.min.js
15 ms
CSSPlugin.min.js
25 ms
LensCrafters_Promo_728x90.css
23 ms
main.js
36 ms
dvtp_src_internal25.js
19 ms
glassesRow.jpg
63 ms
glasses1.png
64 ms
glasses2.png
65 ms
glasses3.png
70 ms
text1.png
64 ms
text2.png
69 ms
ctaText.png
69 ms
logo.png
70 ms
legalOverlay.png
70 ms
border_728x90.png
70 ms
offerDetails.png
70 ms
t2tv7.html
84 ms
visit.js
50 ms
avs546.js
3 ms
event.gif
44 ms
event.jpg
37 ms
ex.inquirer.net accessibility score
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-*] attributes do not match their roles
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ex.inquirer.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ex.inquirer.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ex.inquirer.net 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 Ex.inquirer.net 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.
ex.inquirer.net
Open Graph data is detected on the main page of EX Inquirer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: