Tools & Wizards About Us
tink.se screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

tink.se

Tink | European open banking platform | 6000 connections

Page Load Speed

2 sec in total

First Response

146 ms

Resources Loaded

1.5 sec

Page Rendered

285 ms

tink.se screenshot

About Website

Click here to check amazing Tink content for Spain. Otherwise, check out these important facts you probably never knew about tink.se

Tink’s open banking platform has over 6000 connections to European banks and institutions, and offers enriched and categorised financial data – through 1 API.

Visit tink.se

Key Findings

We analyzed Tink.se page load time and found that the first response time was 146 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

tink.se performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value50.8 s

0/100

25%

SI (Speed Index)

Value47.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value65.8 s

0/100

10%

Network Requests Diagram

tink.se

146 ms

tink.se

288 ms

tink.com

556 ms

fonts.css

350 ms

Edgar_Verschuur-Adyen-Tink-Quote.png

17 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Tink.se, 67% (16 requests) were made to Images.ctfassets.net and 25% (6 requests) were made to Tink.com. The less responsive or slowest element that took the longest time to load (556 ms) relates to the external source Tink.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.8 kB (12%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tink.se main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 227.1 kB

  • Original 291.0 kB
  • After minification 291.0 kB
  • After compression 63.9 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 227.1 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 54.5 kB

  • Original 1.9 MB
  • After minification 1.9 MB

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. Tink images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 82 B

  • Original 128.7 kB
  • After minification 128.7 kB
  • After compression 128.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

-45%

Potential reduce by 144 B

  • Original 323 B
  • After minification 323 B
  • After compression 179 B

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. Tink.se needs all CSS files to be minified and compressed as it can save up to 144 B or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

21

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tink.se

tink.se

146 ms

tink.se

tink.se

288 ms

tink.com

tink.com

556 ms

fonts.css

fonts.css

350 ms

Edgar_Verschuur-Adyen-Tink-Quote.png

Edgar_Verschuur-Adyen-Tink-Quote.png

17 ms

Peer_Timo_Andersen-Ulven-Bank-Norwegian-Tink-Quote.png

Peer_Timo_Andersen-Ulven-Bank-Norwegian-Tink-Quote.png

4 ms

Mattias_Noren-Postnord_Stra_lfors-Tink-Quote.png

Mattias_Noren-Postnord_Stra_lfors-Tink-Quote.png

14 ms

Franc_ois-de-Bodinat-Younited-Tink-Quote2.png

Franc_ois-de-Bodinat-Younited-Tink-Quote2.png

21 ms

Vesna_Lindkvist-Kivra-Tink-Quote.png

Vesna_Lindkvist-Kivra-Tink-Quote.png

21 ms

anPostlight.svg

anPostlight.svg

13 ms

polyfill-b875ed04bb2a71bc6d60.js

polyfill-b875ed04bb2a71bc6d60.js

511 ms

app-4c8597f9e8bb6d42c4fb.js

app-4c8597f9e8bb6d42c4fb.js

533 ms

framework-9d63a51aec966f524e70.js

framework-9d63a51aec966f524e70.js

504 ms

webpack-runtime-3038a1698b562d02d11f.js

webpack-runtime-3038a1698b562d02d11f.js

388 ms

Bruce_Richardson-AnPost-Tink-Quote.png

Bruce_Richardson-AnPost-Tink-Quote.png

16 ms

Cyrill_Chiche-Lydia-Tink-Quote.png

Cyrill_Chiche-Lydia-Tink-Quote.png

17 ms

David_O_hlund-GF-Money-Tink-Quote.png

David_O_hlund-GF-Money-Tink-Quote.png

20 ms

Andreas_Norberg-Rocker-Tink-Quote.png

Andreas_Norberg-Rocker-Tink-Quote.png

18 ms

Stefan_O_berg-Tradera-Tink-Quote.png

Stefan_O_berg-Tradera-Tink-Quote.png

18 ms

Jamie_McNaught-Solidi-Tink-Quote.png

Jamie_McNaught-Solidi-Tink-Quote.png

20 ms

Tim_O_hman_Cirillo-Billogram-Tink-Quote.png

Tim_O_hman_Cirillo-Billogram-Tink-Quote.png

20 ms

Nanna_Stranne-Sigmastocks-Tink-Quote.png

Nanna_Stranne-Sigmastocks-Tink-Quote.png

19 ms

John_Natalizia-Snoop-Tink-Quote__1_.png

John_Natalizia-Snoop-Tink-Quote__1_.png

22 ms

Lending_research_LP_footer_banner.png

Lending_research_LP_footer_banner.png

101 ms

Accessibility Review

tink.se accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best Practices

tink.se 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

Missing source maps for large first-party JavaScript

SEO Factors

tink.se SEO score

75

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

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

    GL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tink.se can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Galician language. Our system also found out that Tink.se 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

tink.se

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