Arcgis.com Test Results

Arcgis.com Mobile Performance: 16/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 434 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 456 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Avoid multiple page redirects. Potential savings of 1,740 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 900 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. Potential savings of 123 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Efficiently encode images. Potential savings of 38 KiB
Optimized images load faster and consume less cellular data. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
4.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
2.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid long main-thread tasks
13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
62 requests • 1,879 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Arcgis.com Mobile SEO: 79/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.

Arcgis.com Mobile Best Practices: 77/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Arcgis.com Mobile Progressive Web App: 18/100
Quick overview:
PWA Optimized
Does not provide fallback content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more. The page body should render some content if its scripts are not available.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 11.5 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Arcgis.com Mobile Accessibility: 82/100
Quick overview:
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Similar sites
Similar tests
www.arcgis.com
www.arcgis.net
www.arcgis.org
www.arcgis.info
www.arcgis.biz
www.arcgis.us
www.arcgis.mobi
www.rcgis.com
www.arcgis.com
www.qrcgis.com
www.aqrcgis.com
www.qarcgis.com
www.wrcgis.com
www.awrcgis.com
www.warcgis.com
www.srcgis.com
www.asrcgis.com
www.sarcgis.com
www.zrcgis.com
www.azrcgis.com
www.zarcgis.com
www.acgis.com
www.aecgis.com
www.arecgis.com
www.aercgis.com
www.adcgis.com
www.ardcgis.com
www.adrcgis.com
www.afcgis.com
www.arfcgis.com
www.afrcgis.com
www.atcgis.com
www.artcgis.com
www.atrcgis.com
www.argis.com
www.arxgis.com
www.arcxgis.com
www.arxcgis.com
www.ardgis.com
www.arcdgis.com
www.arfgis.com
www.arcfgis.com
www.arvgis.com
www.arcvgis.com
www.arvcgis.com
www.arcis.com
www.arcfis.com
www.arcgfis.com
www.arcvis.com
www.arcgvis.com
www.arctis.com
www.arcgtis.com
www.arctgis.com
www.arcbis.com
www.arcgbis.com
www.arcbgis.com
www.arcyis.com
www.arcgyis.com
www.arcygis.com
www.archis.com
www.arcghis.com
www.archgis.com
www.arcgs.com
www.arcgus.com
www.arcgius.com
www.arcguis.com
www.arcgjs.com
www.arcgijs.com
www.arcgjis.com
www.arcgks.com
www.arcgiks.com
www.arcgkis.com
www.arcgos.com
www.arcgios.com
www.arcgois.com
www.arcgi.com
www.arcgiw.com
www.arcgisw.com
www.arcgiws.com
www.arcgie.com
www.arcgise.com
www.arcgies.com
www.arcgid.com
www.arcgisd.com
www.arcgids.com
www.arcgiz.com
www.arcgisz.com
www.arcgizs.com
www.arcgix.com
www.arcgisx.com
www.arcgixs.com
www.arcgia.com
www.arcgisa.com
www.arcgias.com
www.arcgis.con
Last Tested: