3.5 sec in total
384 ms
3 sec
174 ms
Click here to check amazing ING Card content. Otherwise, check out these important facts you probably never knew about ingcard.nl
Creditcard aanvragen? Met een Creditcard zijn al je aankopen verzekerd bij diefstal, schade en verlies. Bekijk hier welke Creditcard het beste bij je past.
Visit ingcard.nlWe analyzed Ingcard.nl page load time and found that the first response time was 384 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster. This domain responded with an error, which can significantly jeopardize Ingcard.nl rating and web reputation
ingcard.nl performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value6.1 s
12/100
25%
Value5.8 s
50/100
10%
Value970 ms
28/100
30%
Value0.634
9/100
15%
Value7.7 s
46/100
10%
384 ms
164 ms
351 ms
31 ms
110 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ingcard.nl, 90% (56 requests) were made to Ing.nl and 6% (4 requests) were made to Tms.ingservices.nl. The less responsive or slowest element that took the longest time to load (989 ms) relates to the external source Mon.ingservices.nl.
Page size can be reduced by 1.9 MB (74%)
2.6 MB
680.5 kB
In fact, the total size of Ingcard.nl main page is 2.6 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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 147.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 37.0 kB, which is 22% 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 147.6 kB or 89% of the original size.
Potential reduce by 30.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. Obviously, ING Card needs image optimization as it can save up to 30.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 904.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 904.7 kB or 73% of the original size.
Potential reduce by 854.9 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. Ingcard.nl needs all CSS files to be minified and compressed as it can save up to 854.9 kB or 87% of the original size.
Number of requests can be reduced by 35 (64%)
55
20
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ING 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 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ingcard.nl
384 ms
164 ms
index.html
351 ms
b05259ab.the-guide-styles-responsive.min.css
31 ms
fonts.css
110 ms
container.css
89 ms
reset-fonts.css
90 ms
sol-1.0.0.css
90 ms
main.css
120 ms
main-override.css
101 ms
comparisonchart.css
106 ms
js.css
100 ms
bootstrap.js
105 ms
jquery-1.10.2.min.js
148 ms
jquery-migrate-1.2.1.min.js
105 ms
jquery-ui-1.11.0.min.js
108 ms
jquery.fancybox.css
105 ms
jquery_extra_libs.js
107 ms
textgrid.css
113 ms
jquery.cookie.js
114 ms
cookie_check.js
105 ms
swfobject.js
113 ms
0d956316.angular-all.js
211 ms
82330caf.spectingular-core.min.js
203 ms
00e90a90.spectingular-components.min.js
204 ms
0568260e.global.ui.min.js
205 ms
9f962d9a.theguide-components.min.js
205 ms
6d49da14.gFooter.apps.min.js
202 ms
5c4f418a.gTopNavigation.apps.min.js
204 ms
cb2ab825.ui-components.apps.min.js
206 ms
le-mtagconfig.js
205 ms
3c695f0d.oRedesignResponsive.apps.min.js
205 ms
general.js
262 ms
htiframemanager.js
207 ms
Foldout.js
206 ms
ing-tooltip.js
206 ms
serverComponent.php
396 ms
bgnd-cookie-bar.png
144 ms
bgnd-cookie-nb-bar.png
142 ms
ING_Mobiel_betalen_198x94_tcm162-96929.jpg
118 ms
img_doelsparen_topnav_tcm162-92919.jpg
120 ms
img_particulier%20beleggen%20visie%202016_tcm162-93428.png
118 ms
ING_NB_hypotheken-campagnebeeld_196X94_tcm162-62656.jpg
119 ms
ING_verbouwen_topnav_198x94_tcm162-62663.jpg
121 ms
ING_Verzekeren_tcm162-62714.gif
118 ms
ING_Q1_Afbeelding%20topnivagatie_196_96_tcm162-94488.png
120 ms
Mobiel%20Bankieren%20ProdNav_tcm162-62682.jpg
120 ms
ING_productuitklapper_Mobiel_betalen_tcm162-73273.jpg
122 ms
INGMeWeb-Regular.woff
119 ms
INGMeWeb-Bold.woff
117 ms
ing-icons-v4-3.woff
117 ms
64404
418 ms
0778915e07beec175de2f81bd306ecb8.js
35 ms
jquery.ba-bbq.min.js
13 ms
5020cde9b448b7a455d82269c40418b2.js
30 ms
b0c6c1f323bbb75c0ea961e8de68e6ad.js
54 ms
wt
989 ms
ING_VID_BT_P_1178_1_AD_15_tcm162-79469.gif
249 ms
ING_creditcards_tcm162-96772.jpg
689 ms
Creditcard_ovz_tcm162-96774.jpg
253 ms
ING_direct-doen_tcm162-96813.jpg
151 ms
print.css
10 ms
ingcard.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
ingcard.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ingcard.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ingcard.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 Ingcard.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.
ingcard.nl
Open Graph data is detected on the main page of ING Card. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: