Tools & Wizards About Us
saltedge.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

saltedge.com

Salt Edge | Open banking for every business

Page Load Speed

3.7 sec in total

First Response

295 ms

Resources Loaded

3.1 sec

Page Rendered

277 ms

saltedge.com screenshot

About Website

Welcome to saltedge.com homepage info - get ready to check Salt Edge best content for Peru right away, or after learning these important things about saltedge.com

Salt Edge’s open banking API solutions enable access to 5,000+ banks globally, empowering businesses create smart services based on data aggregation and payment initiation capabilities.

Visit saltedge.com

Key Findings

We analyzed Saltedge.com page load time and found that the first response time was 295 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

saltedge.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,740 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

saltedge.com

295 ms

saltedge.com

398 ms

www.saltedge.com

483 ms

css

65 ms

frontend-340f88f867b4b748db7793ad7755dae2.css

202 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 79% of them (15 requests) were addressed to the original Saltedge.com, 11% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Saltedge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.9 kB (25%)

Content Size

750.0 kB

After Optimization

559.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 9.9 kB

  • Original 14.0 kB
  • After minification 14.0 kB
  • After compression 4.1 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 9.9 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 3.6 kB

  • Original 502.4 kB
  • After minification 498.8 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. Salt Edge images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-83%

Potential reduce by 177.3 kB

  • Original 212.6 kB
  • After minification 211.6 kB
  • After compression 35.3 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. Saltedge.com needs all CSS files to be minified and compressed as it can save up to 177.3 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Salt Edge. According to our analytics all requests are already optimized.

Network Requests Diagram

saltedge.com

saltedge.com

295 ms

saltedge.com

saltedge.com

398 ms

www.saltedge.com

www.saltedge.com

483 ms

css

css

65 ms

frontend-340f88f867b4b748db7793ad7755dae2.css

frontend-340f88f867b4b748db7793ad7755dae2.css

202 ms

frontend-7b7933302f5040b6b18cccb277c01dd5.js

frontend-7b7933302f5040b6b18cccb277c01dd5.js

849 ms

main-background-1c5582924c3a5f5cba82f9b3ae4f76d1.jpg

main-background-1c5582924c3a5f5cba82f9b3ae4f76d1.jpg

297 ms

saltedge-logo-aec77f40cb3feb58463b49eedb77a332.svg

saltedge-logo-aec77f40cb3feb58463b49eedb77a332.svg

97 ms

spectre-logo-bbf1b58be196b10c814bdabfd3dca29b.svg

spectre-logo-bbf1b58be196b10c814bdabfd3dca29b.svg

193 ms

finext-logo-e846e39858e9a47280cf2e180123be20.svg

finext-logo-e846e39858e9a47280cf2e180123be20.svg

282 ms

qoute-0becb47c507ab964be9b4b872729c2df.svg

qoute-0becb47c507ab964be9b4b872729c2df.svg

281 ms

iliya-yordanov-3344fb4bb0b120554cf991cb7b1070c2.png

iliya-yordanov-3344fb4bb0b120554cf991cb7b1070c2.png

378 ms

saltedge-team-fa0074e4d6107b6b2fc739ba2a4a1edc.png

saltedge-team-fa0074e4d6107b6b2fc739ba2a4a1edc.png

1035 ms

clients-logos-ee28cd857b4c20dcf185659c84d8e735.png

clients-logos-ee28cd857b4c20dcf185659c84d8e735.png

290 ms

social-networks-b479b9295051b5fd1ebc7529c1c7fc1d.svg

social-networks-b479b9295051b5fd1ebc7529c1c7fc1d.svg

373 ms

analytics.js

analytics.js

25 ms

glyphicons-halflings-regular-c971ec56223bd9a869e5966a5d50e3d4.woff

glyphicons-halflings-regular-c971ec56223bd9a869e5966a5d50e3d4.woff

443 ms

collect

collect

3 ms

collect

collect

58 ms

Accessibility Review

saltedge.com accessibility score

68

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

saltedge.com 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

saltedge.com SEO score

88

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

Image elements do not have [alt] attributes

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saltedge.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 Saltedge.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

saltedge.com

Open Graph description is not detected on the main page of Salt Edge. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: