Tools & Wizards About Us
exactly.com screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

exactly.com

Payment acceptance platform tailored exactly for your business

Page Load Speed

2.1 sec in total

First Response

41 ms

Resources Loaded

1.6 sec

Page Rendered

478 ms

exactly.com screenshot

About Website

Click here to check amazing Exactly content. Otherwise, check out these important facts you probably never knew about exactly.com

With exactly®, be able to easily accept online payments on your website or app in EUR, GPB, USD and a variety of other currencies from VISA, MasterCard and APMs

Visit exactly.com

Key Findings

We analyzed Exactly.com page load time and found that the first response time was 41 ms and then it took 2.1 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

exactly.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

exactly.com

41 ms

exactly.com

315 ms

app.css

233 ms

logo-dark.svg

162 ms

gateway.webp

163 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 95% of them (41 requests) were addressed to the original Exactly.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (991 ms) belongs to the original domain Exactly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.7 kB (7%)

Content Size

725.4 kB

After Optimization

672.7 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Exactly.com main page is 725.4 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. 20% of websites need less resources to load. Images take 642.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 52.6 kB

  • Original 62.2 kB
  • After minification 40.8 kB
  • After compression 9.6 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 21.4 kB, which is 34% 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 52.6 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 135 B

  • Original 642.2 kB
  • After minification 642.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. Exactly images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 21.0 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. Exactly.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (12%)

Requests Now

41

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

exactly.com

exactly.com

41 ms

exactly.com

exactly.com

315 ms

app.css

app.css

233 ms

logo-dark.svg

logo-dark.svg

162 ms

gateway.webp

gateway.webp

163 ms

processing.webp

processing.webp

195 ms

account.webp

account.webp

165 ms

open-banking.webp

open-banking.webp

171 ms

recurring.webp

recurring.webp

316 ms

payouts.webp

payouts.webp

316 ms

links.webp

links.webp

320 ms

reporting.webp

reporting.webp

336 ms

affiliate.webp

affiliate.webp

350 ms

chargebacks.webp

chargebacks.webp

384 ms

back-2.png

back-2.png

544 ms

back-3.png

back-3.png

616 ms

main.png

main.png

695 ms

front-1.png

front-1.png

482 ms

css2

css2

32 ms

app.js

app.js

653 ms

pci-dss.webp

pci-dss.webp

533 ms

3ds2.webp

3ds2.webp

633 ms

support-parts-2.png

support-parts-2.png

688 ms

support-parts-1.png

support-parts-1.png

771 ms

support-parts-3.png

support-parts-3.png

768 ms

support-parts-5.png

support-parts-5.png

786 ms

support-parts-0.png

support-parts-0.png

806 ms

support-parts-4.png

support-parts-4.png

768 ms

support-parts-6.png

support-parts-6.png

771 ms

support-parts-7.png

support-parts-7.png

847 ms

support-parts-8.png

support-parts-8.png

923 ms

3d-secure.svg

3d-secure.svg

848 ms

pci-dss.svg

pci-dss.svg

921 ms

arrow-dark.svg

arrow-dark.svg

703 ms

arrow.svg

arrow.svg

650 ms

blured-bg-red.png

blured-bg-red.png

986 ms

blured-bg-blue.png

blured-bg-blue.png

991 ms

instagram.svg

instagram.svg

729 ms

twitter.svg

twitter.svg

761 ms

medium.svg

medium.svg

836 ms

facebook.svg

facebook.svg

855 ms

linkedin.svg

linkedin.svg

805 ms

font

font

19 ms

Accessibility Review

exactly.com accessibility score

92

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

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

SEO Factors

exactly.com SEO score

96

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

exactly.com

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