1 sec in total
40 ms
769 ms
200 ms
Click here to check amazing Ingress content for United States. Otherwise, check out these important facts you probably never knew about ingress.com
Pick a Faction and join a worldwide conflict. Discover. Capture. Build. Collaborate. An AR territory control game by Niantic, makers of Pokémon GO.
Visit ingress.comWe analyzed Ingress.com page load time and found that the first response time was 40 ms and then it took 969 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
ingress.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value7.9 s
3/100
25%
Value3.1 s
93/100
10%
Value510 ms
57/100
30%
Value0.115
86/100
15%
Value8.3 s
40/100
10%
40 ms
159 ms
90 ms
83 ms
118 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 17% of them (5 requests) were addressed to the original Ingress.com, 37% (11 requests) were made to Storage.googleapis.com and 13% (4 requests) were made to Commondatastorage.googleapis.com. The less responsive or slowest element that took the longest time to load (299 ms) relates to the external source Storage.googleapis.com.
Page size can be reduced by 136.1 kB (17%)
801.0 kB
664.9 kB
In fact, the total size of Ingress.com main page is 801.0 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. Images take 558.3 kB which makes up the majority of the site volume.
Potential reduce by 5.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. 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 5.1 kB or 70% of the original size.
Potential reduce by 10.7 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. Ingress images are well optimized though.
Potential reduce by 116.0 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 116.0 kB or 51% of the original size.
Potential reduce by 4.3 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. Ingress.com needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 74% of the original size.
Number of requests can be reduced by 13 (52%)
25
12
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ingress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
ingress.com
40 ms
www.ingress.com
159 ms
js
90 ms
jquery.min.js
83 ms
gen_dashboard_e5c8023daa723ce23479a6671c34b5c8112f9cb7.js
118 ms
css
76 ms
landing.css
140 ms
ga.js
68 ms
icon_events.png
169 ms
icon_fb.png
161 ms
iframe_api
106 ms
icon_twtr.png
207 ms
icon_gplus.png
213 ms
icon_ytube.png
215 ms
icon_store.png
208 ms
icon_support.png
227 ms
ingress_logo.png
230 ms
bg.jpg
256 ms
playbtn_hover_v2.png
218 ms
download_googleplay.png
222 ms
download_appstore.png
252 ms
live_events_banner.png
281 ms
phonev2.png
299 ms
playbtn_default_v2.png
272 ms
__utm.gif
23 ms
__utm.gif
29 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
29 ms
0XxGQsSc1g4rdRdjJKZrNBsxEYwM7FgeyaSgU71cLG0.woff
31 ms
coda_regular.ttf
70 ms
www-widgetapi.js
29 ms
ingress.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
ingress.com 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
General
Impact
Issue
Page has valid source maps
ingress.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ingress.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 Ingress.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.
ingress.com
Open Graph data is detected on the main page of Ingress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: