Usgs.gov Site Title

USGS.gov | Science for a changing world

Usgs.gov Test Results

Usgs.gov Mobile Performance: 33/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Use video formats for animated content. Potential savings of 11,214 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more
Eliminate render-blocking resources. Potential savings of 3,850 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.
Preload key requests. Potential savings of 3,000 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Enable text compression. Potential savings of 234 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Remove unused JavaScript. Potential savings of 285 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Serve images in next-gen formats. Potential savings of 183 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.
Minify JavaScript. Potential savings of 79 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Remove unused CSS. Potential savings of 91 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 62 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.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 390 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Serve static assets with an efficient cache policy
26 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid enormous network payloads
Total size was 12,148 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Minimize main-thread work
3.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid an excessive DOM size
1,047 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Reduce JavaScript execution time
1.9 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
9 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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
45 requests • 12,148 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Usgs.gov Mobile SEO: 73/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Links do not have descriptive text
4 links found
Descriptive link text helps search engines understand your content. Learn more.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
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.
Tap targets are not sized appropriately
20% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Usgs.gov Mobile Best Practices: 54/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. 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.
Does not use HTTPS
1 insecure request 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.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
Usgs.gov Mobile Progressive Web App: 54/100
Quick overview:
PWA Optimized
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.
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: Manifest does not have a PNG icon of at least 512px, Manifest does not have `background_color`.
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. The start_url did respond, but not via a service worker.
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.
Installable
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.
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: Manifest's `display` value is not one of: minimal-ui | fullscreen | standalone, Manifest does not have `short_name`.
Does not use HTTPS
1 insecure request 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.
Usgs.gov Mobile Accessibility: 75/100
Quick overview:
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar tests
www.usgs.com
www.usgs.net
www.usgs.org
www.usgs.info
www.usgs.biz
www.usgs.us
www.usgs.mobi
www.sgs.gov
www.usgs.gov
www.ysgs.gov
www.uysgs.gov
www.yusgs.gov
www.hsgs.gov
www.uhsgs.gov
www.husgs.gov
www.jsgs.gov
www.ujsgs.gov
www.jusgs.gov
www.isgs.gov
www.uisgs.gov
www.iusgs.gov
www.ugs.gov
www.uwgs.gov
www.uswgs.gov
www.uwsgs.gov
www.uegs.gov
www.usegs.gov
www.uesgs.gov
www.udgs.gov
www.usdgs.gov
www.udsgs.gov
www.uzgs.gov
www.uszgs.gov
www.uzsgs.gov
www.uxgs.gov
www.usxgs.gov
www.uxsgs.gov
www.uags.gov
www.usags.gov
www.uasgs.gov
www.uss.gov
www.usfs.gov
www.usgfs.gov
www.usfgs.gov
www.usvs.gov
www.usgvs.gov
www.usvgs.gov
www.usts.gov
www.usgts.gov
www.ustgs.gov
www.usbs.gov
www.usgbs.gov
www.usbgs.gov
www.usys.gov
www.usgys.gov
www.usygs.gov
www.ushs.gov
www.usghs.gov
www.ushgs.gov
www.usg.gov
www.usgw.gov
www.usgsw.gov
www.usgws.gov
www.usge.gov
www.usgse.gov
www.usges.gov
www.usgd.gov
www.usgsd.gov
www.usgds.gov
www.usgz.gov
www.usgsz.gov
www.usgzs.gov
www.usgx.gov
www.usgsx.gov
www.usgxs.gov
www.usga.gov
www.usgsa.gov
www.usgas.gov
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.