Pota.app Site Title

Parks on the Air | POTA

Pota.app Meta Description

Parks program for amateur radio, also known as Parks on the Air (POTA), including a map and list of entities for the program.

Pota.app Test Results

Pota.app Mobile Performance: 31/100
Quick overview:
Max Potential First Input Delay
5,120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
11.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
10,260 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 162 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce JavaScript execution time
7.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Minimize main-thread work
12.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce unused CSS
Potential savings of 36 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Properly size images
Potential savings of 67 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Defer offscreen images
Potential savings of 67 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve static assets with an efficient cache policy
3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Avoid an excessive DOM size
3,964 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Serve images in next-gen formats
Potential savings of 72 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

Pota.app Mobile SEO: 83/100
Quick overview:
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 how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more about canonical links. Is not an absolute URL (/)

Pota.app Mobile Best Practices: 76/100
Quick overview:
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 about this errors in console diagnostic audit
Trust and Safety
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 served over 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 about HTTPS.
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 how to provide responsive images.
Pota.app Mobile Accessibility: 87/100
Quick overview:
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 how to provide sufficient color contrast.
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.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to 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.
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 how to make buttons more accessible.
Similar sites
Similar tests
www.pota.com
www.pota.net
www.pota.org
www.pota.info
www.pota.biz
www.pota.us
www.pota.mobi
www.ota.app
www.pota.app
www.oota.app
www.poota.app
www.opota.app
www.lota.app
www.plota.app
www.lpota.app
www.pta.app
www.pita.app
www.poita.app
www.piota.app
www.pkta.app
www.pokta.app
www.pkota.app
www.plta.app
www.polta.app
www.ppta.app
www.popta.app
www.ppota.app
www.poa.app
www.pora.app
www.potra.app
www.porta.app
www.pofa.app
www.potfa.app
www.pofta.app
www.poga.app
www.potga.app
www.pogta.app
www.poya.app
www.potya.app
www.poyta.app
www.pot.app
www.potq.app
www.potaq.app
www.potqa.app
www.potw.app
www.potaw.app
www.potwa.app
www.pots.app
www.potas.app
www.potsa.app
www.potz.app
www.potaz.app
www.potza.app
Last Tested: