Tools & Wizards About Us
ferratum.dk screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ferratum.dk

Hos Ferratum kan du låne penge nemt og hurtigt | Ferratum Bank

Page Load Speed

4.7 sec in total

First Response

1.3 sec

Resources Loaded

3 sec

Page Rendered

433 ms

ferratum.dk screenshot

About Website

Click here to check amazing Ferratum content for Denmark. Otherwise, check out these important facts you probably never knew about ferratum.dk

Hos Ferratum kan du låne penge hurtigt, nemt og sikkert. Få et hurtigt lån ved at ansøge, og du får svar med det samme.

Visit ferratum.dk

Key Findings

We analyzed Ferratum.dk page load time and found that the first response time was 1.3 sec 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

ferratum.dk performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

ferratum.dk

1333 ms

www.ferratumbank.dk

534 ms

3a09ec0188d76b47.css

39 ms

68955c0fdf604c20.css

35 ms

20b50b9aa63b278d.css

35 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ferratum.dk, 97% (31 requests) were made to Ferratumbank.dk. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ferratum.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.6 kB (20%)

Content Size

507.2 kB

After Optimization

406.6 kB

  • HTML
  • Images

In fact, the total size of Ferratum.dk main page is 507.2 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. 30% of websites need less resources to load. Images take 385.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 100.6 kB

  • Original 122.1 kB
  • After minification 122.0 kB
  • After compression 21.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. 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 100.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 385.0 kB
  • After minification 385.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. Ferratum images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 21 (70%)

Requests Now

30

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ferratum.dk

ferratum.dk

1333 ms

www.ferratumbank.dk

www.ferratumbank.dk

534 ms

3a09ec0188d76b47.css

3a09ec0188d76b47.css

39 ms

68955c0fdf604c20.css

68955c0fdf604c20.css

35 ms

20b50b9aa63b278d.css

20b50b9aa63b278d.css

35 ms

5782cf575e6dd493.css

5782cf575e6dd493.css

29 ms

3b3f332773b5214c.css

3b3f332773b5214c.css

71 ms

102f0e168cf2fd9c.css

102f0e168cf2fd9c.css

49 ms

81c686e7e6ffb974.css

81c686e7e6ffb974.css

50 ms

42ae06268fa78eb2.css

42ae06268fa78eb2.css

46 ms

f8221b7c9f622a4c.css

f8221b7c9f622a4c.css

55 ms

2ba996bad1ed1201.css

2ba996bad1ed1201.css

64 ms

cdbeee709e99e625.css

cdbeee709e99e625.css

66 ms

96e47fb42658cadc.css

96e47fb42658cadc.css

67 ms

005bb3e359fc98ce.css

005bb3e359fc98ce.css

83 ms

1dd3208c-f53a93a1de5feaab.js

1dd3208c-f53a93a1de5feaab.js

77 ms

286-6db6b3cc67250aa6.js

286-6db6b3cc67250aa6.js

86 ms

main-app-42d5d7f9f9c5e71a.js

main-app-42d5d7f9f9c5e71a.js

85 ms

global-error-69e1d193bb994f8d.js

global-error-69e1d193bb994f8d.js

86 ms

773-5fe2c75e0fc9a31c.js

773-5fe2c75e0fc9a31c.js

94 ms

318-c4c0d91bd8d777f6.js

318-c4c0d91bd8d777f6.js

96 ms

page-01e070a6653d8a26.js

page-01e070a6653d8a26.js

97 ms

partytown.js

partytown.js

99 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

453 ms

webpack-0a17238d4057cc97.js

webpack-0a17238d4057cc97.js

58 ms

logo-desktop.svg

logo-desktop.svg

328 ms

image

image

610 ms

fe-logo-mobile-blue.svg

fe-logo-mobile-blue.svg

330 ms

image

image

504 ms

image

image

525 ms

image

image

523 ms

image

image

683 ms

Accessibility Review

ferratum.dk accessibility score

69

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

Form elements do not have associated labels

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

ferratum.dk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ferratum.dk 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

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

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

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

ferratum.dk

Open Graph description is not detected on the main page of Ferratum. 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: