2.8 sec in total
79 ms
2.5 sec
244 ms
Click here to check amazing Citi Card content for United States. Otherwise, check out these important facts you probably never knew about citicard.com
Compare Citi credit card offers or login to your existing account. Explore a variety of features and benefits you can take advantage of as a Citi credit card member.
Visit citicard.comWe analyzed Citicard.com page load time and found that the first response time was 79 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Citicard.com rating and web reputation
citicard.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value33.1 s
0/100
25%
Value18.4 s
0/100
10%
Value5,430 ms
0/100
30%
Value0.231
54/100
15%
Value35.0 s
0/100
10%
79 ms
303 ms
96 ms
72 ms
22 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Citicard.com, 44% (46 requests) were made to Citi.com and 11% (11 requests) were made to Chat.online.citi.com. The less responsive or slowest element that took the longest time to load (316 ms) relates to the external source Mpsnare.iesnare.com.
Page size can be reduced by 3.2 MB (81%)
3.9 MB
758.7 kB
In fact, the total size of Citicard.com main page is 3.9 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 154.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. This page needs HTML code to be minified as it can gain 27.2 kB, which is 15% 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 154.1 kB or 85% of the original size.
Potential reduce by 30.5 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, Citi Card needs image optimization as it can save up to 30.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.8 MB
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 1.8 MB or 80% of the original size.
Potential reduce by 1.2 MB
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. Citicard.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 92% of the original size.
Number of requests can be reduced by 71 (72%)
98
27
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citi 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 45 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
citicard.com
79 ms
citi.action
303 ms
19469
96 ms
Bootstrap.js
72 ms
jquery-1.7.2.js
22 ms
jfp.branding.js
43 ms
jquery-ui-1.8.18.js
47 ms
jfp.widgets.js
49 ms
ShopCookie.js
46 ms
JPPWidget.css
41 ms
amw.js
42 ms
SitecatCampaigns.js
50 ms
AOSDMP.js
54 ms
CitiCards_sass.css
55 ms
CitiCards_sass_res.css
61 ms
normalize.css
54 ms
jfpw.tooltip.css
64 ms
btAdServe.js
57 ms
CitiCommonMkt.js
62 ms
vendors.top.min.js
57 ms
som-banners.css
60 ms
mbox.js
64 ms
s_code.js
60 ms
rmegamenu.js
62 ms
branding_universal.js
63 ms
vendors.bot.min.js
59 ms
mainMkt.js
74 ms
mtagconfig.js
63 ms
serverComponent.php
99 ms
navigation.js
166 ms
style4.js
89 ms
target.js
90 ms
b580a183f0efc2ef58811bafb2821f2d.js
23 ms
aca430d8650f0b330b8e732bc32f7b6f.js
39 ms
standard
104 ms
citi_logo.png
61 ms
Red_GlobalAlert_Icon.png
295 ms
ServerError.html
69 ms
standard
14 ms
standard
12 ms
trackconversion
5 ms
citi-simplicity-credit-card.png
283 ms
citi-double-cash-credit-card.png
32 ms
citi-aadvantage-platinum-select-credit-card.png
39 ms
header_blueWave.jpg
56 ms
sprites.png
23 ms
bg_shadow_nav.png
22 ms
browser_mess_pattern.gif
54 ms
generalErrorJSE2.do
232 ms
Interstate-Regular.woff
246 ms
Interstate-Light.woff
268 ms
preloader.gif
27 ms
content-block-separator.jpg
26 ms
adchoice-ccc.png
200 ms
snare.js
316 ms
citi.action
270 ms
gr_signOn_horizontal_seperator.png
49 ms
OL_Close_Btn.png
50 ms
dd-dynamic-single-fam3-lg-bg.jpg
37 ms
card-stack-icon.png
61 ms
img;m=11042201469692;cache=
46 ms
Interstate-Bold.woff
150 ms
s81690691427793
17 ms
pixel
268 ms
logo.js
59 ms
156 ms
spp.pl
177 ms
activity;src=1862678;dcnet=4856;boom=48267;sz=1x1;ord=7287451401.352882
115 ms
16329
34 ms
hbpix
158 ms
fbds.js
220 ms
beacon
174 ms
deploy2.asp
156 ms
a.js;m=11042207321713;cache=0.7803788366727531
45 ms
58 ms
DTZ.html
85 ms
img;p=11042207348223;a=11042207348244;cache=
48 ms
86 ms
iui3
53 ms
img;m=11042207125362;cache=
37 ms
startseitep=plloydsbank
25 ms
23 ms
login
34 ms
44 ms
16 ms
img
54 ms
img
54 ms
mTag.js
13 ms
49 ms
17 ms
115 ms
pixel
47 ms
pixel
28 ms
27 ms
22 ms
27 ms
28 ms
95 ms
81 ms
74 ms
73 ms
csesb
9 ms
csesb
38 ms
compare-button.gif
36 ms
citicard.com accessibility score
citicard.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
citicard.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citicard.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 Citicard.com main page’s claimed encoding is iso-8859-1. 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.
citicard.com
Open Graph data is detected on the main page of Citi Card. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: