Tools & Wizards About Us
theworldcard.nl screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

theworldcard.nl

Visa World Card: voor wereldwijd betaalgemak Visa World Card | International Card Services

Page Load Speed

4.7 sec in total

First Response

267 ms

Resources Loaded

4.1 sec

Page Rendered

346 ms

theworldcard.nl screenshot

About Website

Welcome to theworldcard.nl homepage info - get ready to check The World Card best content right away, or after learning these important things about theworldcard.nl

De Visa World Card is 's werelds meest geaccepteerde creditcard. Deze creditcard biedt u een aantal fantastische voordelen.

Visit theworldcard.nl

Key Findings

We analyzed Theworldcard.nl page load time and found that the first response time was 267 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

theworldcard.nl performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value3,340 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

theworldcard.nl

267 ms

www.worldcard.nl

664 ms

main-worldcard.css

457 ms

modernizr.js

402 ms

tp.widget.bootstrap.min.js

31 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Theworldcard.nl, 55% (21 requests) were made to Worldcard.nl and 13% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Worldcard.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.0 kB (22%)

Content Size

353.3 kB

After Optimization

275.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Theworldcard.nl main page is 353.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 233.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 45.8 kB

  • Original 61.3 kB
  • After minification 51.7 kB
  • After compression 15.4 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 9.6 kB, which is 16% 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 45.8 kB or 75% of the original size.

JavaScript Optimization

-14%

Potential reduce by 32.2 kB

  • Original 233.4 kB
  • After minification 233.2 kB
  • After compression 201.3 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 32.2 kB or 14% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 58.6 kB
  • After minification 58.6 kB
  • After compression 58.6 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. Theworldcard.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (34%)

Requests Now

29

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

theworldcard.nl

theworldcard.nl

267 ms

www.worldcard.nl

www.worldcard.nl

664 ms

main-worldcard.css

main-worldcard.css

457 ms

modernizr.js

modernizr.js

402 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

31 ms

jquery.min.js

jquery.min.js

32 ms

bootstrap.min.js

bootstrap.min.js

44 ms

main.js

main.js

551 ms

gtm.js

gtm.js

178 ms

PaxTHfvwDFQ

PaxTHfvwDFQ

170 ms

herobanner_lekkerweg_1920x510.png

herobanner_lekkerweg_1920x510.png

512 ms

card-afbeelding-worldcard-met-actiebol_zorgeloosbetalen_280x165.png

card-afbeelding-worldcard-met-actiebol_zorgeloosbetalen_280x165.png

513 ms

card-afbeelding-worldcard-met-actiebol_zorgeloosbetalen_350x220.png

card-afbeelding-worldcard-met-actiebol_zorgeloosbetalen_350x220.png

543 ms

smiley-face-duo.svg

smiley-face-duo.svg

544 ms

rating-stars.svg

rating-stars.svg

555 ms

ics%3Aoffermedium

ics%3Aoffermedium

766 ms

ics%3Aoffermedium

ics%3Aoffermedium

928 ms

ics%3Aoffermedium

ics%3Aoffermedium

929 ms

ics%3Aoffermedium

ics%3Aoffermedium

1058 ms

ics%3Aoffermedium

ics%3Aoffermedium

984 ms

logo-ics.gif

logo-ics.gif

1017 ms

aeonik-medium.woff

aeonik-medium.woff

1114 ms

aeonik-regular.woff

aeonik-regular.woff

1156 ms

aeonik-bold.woff

aeonik-bold.woff

1211 ms

icons.woff

icons.woff

1221 ms

ics-icons-2023.woff

ics-icons-2023.woff

1250 ms

herobanner_lekkerweg_1920x510.png

herobanner_lekkerweg_1920x510.png

2524 ms

www-player.css

www-player.css

11 ms

www-embed-player.js

www-embed-player.js

33 ms

base.js

base.js

61 ms

ad_status.js

ad_status.js

164 ms

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

137 ms

embed.js

embed.js

48 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

56 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

56 ms

id

id

26 ms

Create

Create

171 ms

GenerateIT

GenerateIT

15 ms

Accessibility Review

theworldcard.nl accessibility score

81

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

ARIA input fields do not have accessible names

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

theworldcard.nl best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

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

theworldcard.nl SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

theworldcard.nl

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