Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fluidly.com

Partnering With Us | OakNorth Bank

Page Load Speed

1.9 sec in total

First Response

18 ms

Resources Loaded

1.5 sec

Page Rendered

317 ms

fluidly.com screenshot

About Website

Click here to check amazing Fluidly content for India. Otherwise, check out these important facts you probably never knew about fluidly.com

Our partnership scheme allows advisors and accountants to connect their clients with a flexible finance provider and reap the benefits.

Visit fluidly.com

Key Findings

We analyzed Fluidly.com page load time and found that the first response time was 18 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

fluidly.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value3,290 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

fluidly.com

18 ms

244 ms

163 ms

gtm.js

129 ms

datadog-rum-v4.js

71 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fluidly.com, 39% (18 requests) were made to Oaknorth.co.uk and 11% (5 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (640 ms) relates to the external source Js-eu1.hsforms.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.2 kB (32%)

Content Size

581.6 kB

After Optimization

395.4 kB

In fact, the total size of Fluidly.com main page is 581.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 227.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 184.5 kB

  • Original 213.0 kB
  • After minification 161.2 kB
  • After compression 28.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 51.8 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 184.5 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 57.0 kB
  • After minification 57.0 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Fluidly images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 227.3 kB
  • After minification 227.3 kB
  • After compression 225.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 19 B

  • Original 84.2 kB
  • After minification 84.2 kB
  • After compression 84.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fluidly.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (82%)

Requests Now

34

After Optimization

6

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fluidly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

fluidly.com accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

Impact

Issue

High

Links do not have a discernible name

Best Practices

fluidly.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fluidly.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fluidly.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fluidly.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Fluidly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: