Footlocker.sg Test Results

Footlocker.sg Mobile Performance: 1/100
Quick overview:
Max Potential First Input Delay
2,090 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
42.1 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.
First Meaningful Paint
5.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Network Round Trip Times
30 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.
Server Backend Latencies
670 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.
Script Treemap Data
Used for treemap app
Tasks
Lists the toplevel main thread tasks that executed during page load.
Metrics
Collects all available metrics.
Resources Summary
Aggregates all network requests and groups them by type
Final Screenshot
The last screenshot captured of the pageload.

308949108208

Diagnostics
Collection of useful page vitals.
Network Requests
Lists the network requests that were made during page load.

Footlocker.sg Mobile SEO: 93/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

Footlocker.sg Mobile Best Practices: 33/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
Uses third-party cookies
2 cookies found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more about unload event listeners
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
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Footlocker.sg Mobile PWA: 38/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. 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 about splash screens. 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 about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Footlocker.sg Mobile Accessibility: 71/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.
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.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
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 about roles and required children elements.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn how to fix duplicate `id`s.
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.
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 tests
www.footlocker.com
www.footlocker.net
www.footlocker.org
www.footlocker.info
www.footlocker.biz
www.footlocker.us
www.footlocker.mobi
www.ootlocker.sg
www.footlocker.sg
www.cootlocker.sg
www.fcootlocker.sg
www.cfootlocker.sg
www.dootlocker.sg
www.fdootlocker.sg
www.dfootlocker.sg
www.rootlocker.sg
www.frootlocker.sg
www.rfootlocker.sg
www.tootlocker.sg
www.ftootlocker.sg
www.tfootlocker.sg
www.gootlocker.sg
www.fgootlocker.sg
www.gfootlocker.sg
www.vootlocker.sg
www.fvootlocker.sg
www.vfootlocker.sg
www.fotlocker.sg
www.fiotlocker.sg
www.foiotlocker.sg
www.fiootlocker.sg
www.fkotlocker.sg
www.fokotlocker.sg
www.fkootlocker.sg
www.flotlocker.sg
www.folotlocker.sg
www.flootlocker.sg
www.fpotlocker.sg
www.fopotlocker.sg
www.fpootlocker.sg
www.foitlocker.sg
www.fooitlocker.sg
www.foktlocker.sg
www.fooktlocker.sg
www.foltlocker.sg
www.fooltlocker.sg
www.foptlocker.sg
www.fooptlocker.sg
www.foolocker.sg
www.foorlocker.sg
www.footrlocker.sg
www.foortlocker.sg
www.fooflocker.sg
www.footflocker.sg
www.fooftlocker.sg
www.fooglocker.sg
www.footglocker.sg
www.foogtlocker.sg
www.fooylocker.sg
www.footylocker.sg
www.fooytlocker.sg
www.footocker.sg
www.footpocker.sg
www.footlpocker.sg
www.footplocker.sg
www.footoocker.sg
www.footloocker.sg
www.footolocker.sg
www.footkocker.sg
www.footlkocker.sg
www.footklocker.sg
www.footlcker.sg
www.footlicker.sg
www.footloicker.sg
www.footliocker.sg
www.footlkcker.sg
www.footlokcker.sg
www.footllcker.sg
www.footlolcker.sg
www.footllocker.sg
www.footlpcker.sg
www.footlopcker.sg
www.footloker.sg
www.footloxker.sg
www.footlocxker.sg
www.footloxcker.sg
www.footlodker.sg
www.footlocdker.sg
www.footlodcker.sg
www.footlofker.sg
www.footlocfker.sg
www.footlofcker.sg
www.footlovker.sg
www.footlocvker.sg
www.footlovcker.sg
www.footlocer.sg
www.footlocjer.sg
www.footlockjer.sg
www.footlocjker.sg
www.footlocier.sg
www.footlockier.sg
www.footlociker.sg
www.footlocmer.sg
www.footlockmer.sg
www.footlocmker.sg
www.footlocler.sg
www.footlockler.sg
www.footloclker.sg
www.footlocoer.sg
www.footlockoer.sg
www.footlocoker.sg
www.footlockr.sg
www.footlockwr.sg
www.footlockewr.sg
www.footlockwer.sg
www.footlocksr.sg
www.footlockesr.sg
www.footlockser.sg
www.footlockdr.sg
www.footlockedr.sg
www.footlockder.sg
www.footlockrr.sg
www.footlockerr.sg
www.footlockrer.sg
www.footlocke.sg
www.footlockee.sg
www.footlockere.sg
www.footlockeer.sg
www.footlocked.sg
www.footlockerd.sg
www.footlockef.sg
www.footlockerf.sg
www.footlockefr.sg
www.footlocket.sg
www.footlockert.sg
www.footlocketr.sg
Last Tested: