fi.money

Fi.money Site Title

Fi.money Meta Description

Bank on Fi - Get better with money

Fi.money Test Results

Fi.money Mobile Performance: 18/100

Quick overview:

Opportunities

These suggestions can help your page load faster. They don't directly affect the Performance score.

Serve images in next-gen formats. Potential savings of 772 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.

Properly size images. Potential savings of 640 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused JavaScript. Potential savings of 193 KiB

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Reduce initial server response time. Root document took 1,030 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Diagnostics

More information about the performance of your application. These numbers don't directly affect the Performance score.

Minimize main-thread work

6.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Reduce JavaScript execution time

3.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 an excessive DOM size

1,055 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Serve static assets with an efficient cache policy

1 resource found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Avoid enormous network payloads

Total size was 2,881 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Avoid large layout shifts

5 elements found

These DOM elements contribute most to the CLS of the page.

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

39 requests • 2,881 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Avoid chaining critical requests

7 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

Fi.money Mobile SEO: 92/100

Quick overview:

Crawling and Indexing

To appear in search results, crawlers need access to your app.

robots.txt is not valid

1 error found

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.

Fi.money Mobile Best Practices: 79/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 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.

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.

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.

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

Fi.money Mobile Progressive Web App: 46/100

Quick overview:

Installable

Does not use HTTPS

1 insecure request found

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: No manifest was fetched.

PWA Optimized

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: No manifest was fetched.

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. 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. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

Does not provide a valid `apple-touch-icon`

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

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. No usable web app manifest found on page.

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.

Fi.money Mobile Accessibility: 91/100

Quick overview:

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 more.

The page does not contain a heading, skip link, or landmark region

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. 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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

`<html>` element does not have a `[lang]` attribute

If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.

Similar tests

www.fi.com
www.fi.net
www.fi.org
www.fi.info
www.fi.biz
www.fi.us
www.fi.mobi
www.i.money
www.fi.money
www.ci.money
www.fci.money
www.cfi.money
www.di.money
www.fdi.money
www.dfi.money
www.ri.money
www.fri.money
www.rfi.money
www.ti.money
www.fti.money
www.tfi.money
www.gi.money
www.fgi.money
www.gfi.money
www.vi.money
www.fvi.money
www.vfi.money
www.f.money
www.fu.money
www.fiu.money
www.fui.money
www.fj.money
www.fij.money
www.fji.money
www.fk.money
www.fik.money
www.fki.money
www.fo.money
www.fio.money
www.foi.money