Tools & Wizards About Us
amicable.io screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

amicable.io

amicable | Divorce, Separation and Cooperative Parenting

Page Load Speed

1.9 sec in total

First Response

38 ms

Resources Loaded

1.6 sec

Page Rendered

298 ms

amicable.io screenshot

About Website

Click here to check amazing Amicable content. Otherwise, check out these important facts you probably never knew about amicable.io

Choose amicable to divorce without solicitors. The online divorce service helps couples reach an agreement amicably. Save money with fixed and transparent fees and flexible payments. Get a successful ...

Visit amicable.io

Key Findings

We analyzed Amicable.io page load time and found that the first response time was 38 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

amicable.io performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.173

69/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

amicable.io

38 ms

amicable.io

369 ms

amicable-new-website-2023.316bed767.min.css

50 ms

webfont.js

38 ms

uc.js

59 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Amicable.io, 27% (15 requests) were made to Cdn.prod.website-files.com and 14% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (756 ms) relates to the external source T01.amicable.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.2 kB (23%)

Content Size

751.9 kB

After Optimization

577.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amicable.io main page is 751.9 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. Only a small number of websites need less resources to load. Javascripts take 534.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 88.5 kB

  • Original 108.3 kB
  • After minification 103.4 kB
  • After compression 19.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 88.5 kB or 82% of the original size.

Image Optimization

-45%

Potential reduce by 5.4 kB

  • Original 12.0 kB
  • After minification 6.6 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. Obviously, Amicable needs image optimization as it can save up to 5.4 kB or 45% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 80.3 kB

  • Original 534.8 kB
  • After minification 534.8 kB
  • After compression 454.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.3 kB or 15% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 96.8 kB
  • After minification 96.8 kB
  • After compression 96.8 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. Amicable.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (63%)

Requests Now

43

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amicable.io

amicable.io

38 ms

amicable.io

amicable.io

369 ms

amicable-new-website-2023.316bed767.min.css

amicable-new-website-2023.316bed767.min.css

50 ms

webfont.js

webfont.js

38 ms

uc.js

uc.js

59 ms

cd.js

cd.js

145 ms

js

js

92 ms

js

js

187 ms

25966546.js

25966546.js

443 ms

email-decode.min.js

email-decode.min.js

9 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

40 ms

amicable-new-website-2023.0f84af215.js

amicable-new-website-2023.0f84af215.js

91 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

40 ms

dev.js

dev.js

399 ms

brand-remove.js

brand-remove.js

756 ms

css

css

50 ms

fbevents.js

fbevents.js

100 ms

hotjar-3137506.js

hotjar-3137506.js

164 ms

array.js

array.js

125 ms

63a1dddfb822c00400efb5bf_Vector%2017.svg

63a1dddfb822c00400efb5bf_Vector%2017.svg

32 ms

65d4d782c01734c943a55b45_Amicable%20Octopus%20Money%20Main%20Logo.svg

65d4d782c01734c943a55b45_Amicable%20Octopus%20Money%20Main%20Logo.svg

82 ms

63a32c0e5f306efb9e9dc66e_Polygon%201.svg

63a32c0e5f306efb9e9dc66e_Polygon%201.svg

109 ms

638f0d9f6afc761adf1b01a5_image%20(17).png

638f0d9f6afc761adf1b01a5_image%20(17).png

110 ms

63a1de2e6bb694501248f689_Frame%201475.svg

63a1de2e6bb694501248f689_Frame%201475.svg

110 ms

63a2c1951084674495a62867_Vector%2016.svg

63a2c1951084674495a62867_Vector%2016.svg

112 ms

63a1f2dff7ad6da7bd973841_Frame%201357.svg

63a1f2dff7ad6da7bd973841_Frame%201357.svg

108 ms

63a1ed8870096664c371911f_Group%201145.svg

63a1ed8870096664c371911f_Group%201145.svg

112 ms

63a1ed884e8237ca6f9f4c98_Group%201145-1.svg

63a1ed884e8237ca6f9f4c98_Group%201145-1.svg

143 ms

63a1ed8848b1cb349f8daccf_Frame%2011.svg

63a1ed8848b1cb349f8daccf_Frame%2011.svg

142 ms

cdreport.js

cdreport.js

196 ms

638e00ce8b80d8e8db7c2621_Solomon%20Sans%20Normal.otf

638e00ce8b80d8e8db7c2621_Solomon%20Sans%20Normal.otf

94 ms

638e00c44f9b6d66a2f7d756_Solomon%20Sans%20Book.otf

638e00c44f9b6d66a2f7d756_Solomon%20Sans%20Book.otf

94 ms

638f569b6076f35833146202_Solomon%20Sans%20Bold.otf

638f569b6076f35833146202_Solomon%20Sans%20Bold.otf

93 ms

4iCv6KVjbNBYlgoC1CzjsGyL.woff

4iCv6KVjbNBYlgoC1CzjsGyL.woff

75 ms

4iCs6KVjbNBYlgoKfw7w.woff

4iCs6KVjbNBYlgoKfw7w.woff

90 ms

4iCv6KVjbNBYlgoCjC3jsGyL.woff

4iCv6KVjbNBYlgoCjC3jsGyL.woff

114 ms

4iCv6KVjbNBYlgoCxCvjsGyL.woff

4iCv6KVjbNBYlgoCxCvjsGyL.woff

116 ms

4iCp6KVjbNBYlgoKejZftVyPN4c.woff

4iCp6KVjbNBYlgoKejZftVyPN4c.woff

115 ms

4iCu6KVjbNBYlgoKej70l08.woff

4iCu6KVjbNBYlgoKej70l08.woff

116 ms

4iCp6KVjbNBYlgoKejYHtFyPN4c.woff

4iCp6KVjbNBYlgoKejYHtFyPN4c.woff

116 ms

4iCp6KVjbNBYlgoKejZPslyPN4c.woff

4iCp6KVjbNBYlgoKejZPslyPN4c.woff

115 ms

630 ms

banner.js

banner.js

424 ms

conversations-embed.js

conversations-embed.js

417 ms

25966546.js

25966546.js

429 ms

collectedforms.js

collectedforms.js

427 ms

web-interactives-embed.js

web-interactives-embed.js

503 ms

fb.js

fb.js

441 ms

iframe_api

iframe_api

36 ms

www-widgetapi.js

www-widgetapi.js

5 ms

EbTnvdkRIBQ

EbTnvdkRIBQ

111 ms

recorder.js

recorder.js

13 ms

web-vitals.js

web-vitals.js

22 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

34 ms

base.js

base.js

54 ms

Accessibility Review

amicable.io accessibility score

88

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

amicable.io best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

amicable.io 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 Amicable.io 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 Amicable.io 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

amicable.io

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