2.4 sec in total
347 ms
1.6 sec
415 ms
Welcome to faq.wwr.mobi homepage info - get ready to check Faq Wwr best content for Mexico right away, or after learning these important things about faq.wwr.mobi
True 6v6 multiplayer action with giant walking robots that can fit on palm of your hand? Easy!
Visit faq.wwr.mobiWe analyzed Faq.wwr.mobi page load time and found that the first response time was 347 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
faq.wwr.mobi performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value7.5 s
4/100
25%
Value10.1 s
9/100
10%
Value1,150 ms
22/100
30%
Value0
100/100
15%
Value12.3 s
15/100
10%
347 ms
171 ms
334 ms
64 ms
72 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Faq.wwr.mobi, 83% (30 requests) were made to P3.zdassets.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (568 ms) relates to the external source Wwrpixonic.zendesk.com.
Page size can be reduced by 577.5 kB (70%)
828.6 kB
251.1 kB
In fact, the total size of Faq.wwr.mobi main page is 828.6 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. 55% of websites need less resources to load. Javascripts take 734.1 kB which makes up the majority of the site volume.
Potential reduce by 35.1 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 7.9 kB, which is 18% 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 35.1 kB or 79% of the original size.
Potential reduce by 506.7 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 506.7 kB or 69% of the original size.
Potential reduce by 35.7 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. Faq.wwr.mobi needs all CSS files to be minified and compressed as it can save up to 35.7 kB or 72% of the original size.
Number of requests can be reduced by 6 (19%)
32
26
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faq Wwr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
faq.wwr.mobi
347 ms
hc
171 ms
en-us
334 ms
application-80c7aad11baf60732a806f5ba7f66d94.css
64 ms
style-9c04a6dea25d9717bc90917eb6d105fc.css
72 ms
jquery-ded366808f7e9b8657865f599dda349a.js
88 ms
script-9c04a6dea25d9717bc90917eb6d105fc.js
79 ms
locales-dac712b042e8667e923847da41eb3a9080dcaa72.js
69 ms
host.js
568 ms
vendor_enduser-2ece5393630b699856d9e895b8a3cc1e.js
162 ms
hc_enduser-e7e646dd454b715a8f77941eda299930.js
162 ms
analytics.js
22 ms
faq_bg.jpg
218 ms
header.png
167 ms
store-buttons3.png
40 ms
soc-buttons4.png
112 ms
pXVYEZJP9SYxw8UCimMNKg-logo.png
58 ms
search.png
59 ms
header-light.png
109 ms
CARNAGE-5.png
166 ms
promoted2-2.png
173 ms
promoted2-3.png
219 ms
arrow.png
139 ms
arrow-related.png
167 ms
footer-light.png
224 ms
footer-left.png
193 ms
footer-lamp.png
194 ms
collect
13 ms
entypo.svg
199 ms
entypo.woff
180 ms
robot-suspension-1.png
35 ms
robot-suspension-2.png
30 ms
robot-suspension-3.png
32 ms
robot-wp.png
30 ms
robot-assault.png
31 ms
robot-stealth.png
30 ms
faq.wwr.mobi accessibility score
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
Buttons do not have an accessible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
faq.wwr.mobi best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
faq.wwr.mobi SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faq.wwr.mobi 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 Faq.wwr.mobi 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.
faq.wwr.mobi
Open Graph description is not detected on the main page of Faq Wwr. 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: