Lockly.com Test Results

Lockly.com Mobile Performance: 28/100
Quick overview:
Time to Interactive
32.3 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.
Max Potential First Input Delay
1,250 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.
First Meaningful Paint
5.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Metrics
Collects all available metrics.
Final Screenshot
The last screenshot captured of the pageload.

973116273792

Script Treemap Data
Used for treemap app
Network Round Trip Times
430 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Network Requests
Lists the network requests that were made during page load.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Server Backend Latencies
1,100 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Diagnostics
Collection of useful page vitals.

Lockly.com Mobile SEO: 77/100
Quick overview:
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
94% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
5 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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 about the `alt` attribute.
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

Lockly.com Mobile Best Practices: 68/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
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection 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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Lockly.com Mobile PWA: 63/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 about maskable manifest icons.
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 about splash screens. Failures: Manifest does not have a PNG icon of at least 512px, Manifest does not have `background_color`, Manifest does not have `theme_color`, Manifest does not have `name`.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: Manifest does not have `theme_color`.
Lockly.com Mobile Accessibility: 72/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.
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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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 about the `alt` attribute.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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.
`[role]`s are not contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Touch targets have sufficient size and 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 sites
Similar tests
www.lockly.com
www.lockly.net
www.lockly.org
www.lockly.info
www.lockly.biz
www.lockly.us
www.lockly.mobi
www.ockly.com
www.lockly.com
www.pockly.com
www.lpockly.com
www.plockly.com
www.oockly.com
www.loockly.com
www.olockly.com
www.kockly.com
www.lkockly.com
www.klockly.com
www.lckly.com
www.lickly.com
www.loickly.com
www.liockly.com
www.lkckly.com
www.lokckly.com
www.llckly.com
www.lolckly.com
www.llockly.com
www.lpckly.com
www.lopckly.com
www.lokly.com
www.loxkly.com
www.locxkly.com
www.loxckly.com
www.lodkly.com
www.locdkly.com
www.lodckly.com
www.lofkly.com
www.locfkly.com
www.lofckly.com
www.lovkly.com
www.locvkly.com
www.lovckly.com
www.locly.com
www.locjly.com
www.lockjly.com
www.locjkly.com
www.locily.com
www.lockily.com
www.locikly.com
www.locmly.com
www.lockmly.com
www.locmkly.com
www.loclly.com
www.locklly.com
www.loclkly.com
www.locoly.com
www.lockoly.com
www.locokly.com
www.locky.com
www.lockpy.com
www.locklpy.com
www.lockply.com
www.lockoy.com
www.lockloy.com
www.lockky.com
www.locklky.com
www.lockkly.com
www.lockl.com
www.locklt.com
www.locklyt.com
www.locklty.com
www.locklg.com
www.locklyg.com
www.locklgy.com
www.locklh.com
www.locklyh.com
www.locklhy.com
www.locklu.com
www.locklyu.com
www.lockluy.com
www.lockly.con
Last Tested: