Helma.org Test Results

Helma.org Mobile Performance: 92/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 initial server response time
Root document took 1,740 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Largest Contentful Paint element
2,760 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 10 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.
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.
Max Potential First Input Delay
170 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.

Helma.org Mobile SEO: 92/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

Helma.org Mobile Best Practices: 83/100
Quick overview:
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.
Helma.org Mobile Accessibility: 90/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.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar tests
www.helma.com
www.helma.net
www.helma.org
www.helma.info
www.helma.biz
www.helma.us
www.helma.mobi
www.elma.org
www.helma.org
www.belma.org
www.hbelma.org
www.bhelma.org
www.gelma.org
www.hgelma.org
www.ghelma.org
www.yelma.org
www.hyelma.org
www.yhelma.org
www.uelma.org
www.huelma.org
www.uhelma.org
www.jelma.org
www.hjelma.org
www.jhelma.org
www.nelma.org
www.hnelma.org
www.nhelma.org
www.hlma.org
www.hwlma.org
www.hewlma.org
www.hwelma.org
www.hslma.org
www.heslma.org
www.hselma.org
www.hdlma.org
www.hedlma.org
www.hdelma.org
www.hrlma.org
www.herlma.org
www.hrelma.org
www.hema.org
www.hepma.org
www.helpma.org
www.heplma.org
www.heoma.org
www.heloma.org
www.heolma.org
www.hekma.org
www.helkma.org
www.heklma.org
www.hela.org
www.helna.org
www.helmna.org
www.helnma.org
www.helja.org
www.helmja.org
www.heljma.org
www.helka.org
www.helmka.org
www.helm.org
www.helmq.org
www.helmaq.org
www.helmqa.org
www.helmw.org
www.helmaw.org
www.helmwa.org
www.helms.org
www.helmas.org
www.helmsa.org
www.helmz.org
www.helmaz.org
www.helmza.org
Last Tested: