Tools & Wizards About Us
citicards.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

citicards.com

Citi Credit Cards – Find the right Credit Card for you – Citi.com

Page Load Speed

46 sec in total

First Response

457 ms

Resources Loaded

37.9 sec

Page Rendered

7.6 sec

citicards.com screenshot

About Website

Visit citicards.com now to see the best up-to-date Citi Cards content for United States and also check out these interesting facts you probably never knew about citicards.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 citicards.com

Key Findings

We analyzed Citicards.com page load time and found that the first response time was 457 ms and then it took 45.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

citicards.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value29.4 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value17,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.242

51/100

15%

TTI (Time to Interactive)

Value38.3 s

0/100

10%

Network Requests Diagram

citicards.com

457 ms

citi.action

666 ms

CitiCards_sass.css

414 ms

CitiCards_sass_res.css

1308 ms

jquery-1.7.2.js

1535 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Citicards.com, 33% (36 requests) were made to Citi.com and 12% (13 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source A.rfihub.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.4 MB (78%)

Content Size

5.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Citicards.com main page is 5.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. 75% 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 125.7 kB

  • Original 148.3 kB
  • After minification 125.4 kB
  • After compression 22.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 22.9 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 125.7 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 39.2 kB

  • Original 441.7 kB
  • After minification 402.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. Citi Cards images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 2.2 MB

  • Original 2.8 MB
  • After minification 2.5 MB
  • After compression 569.6 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 2.2 MB or 79% of the original size.

CSS Optimization

-91%

Potential reduce by 2.0 MB

  • Original 2.2 MB
  • After minification 1.7 MB
  • After compression 208.0 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. Citicards.com needs all CSS files to be minified and compressed as it can save up to 2.0 MB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (75%)

Requests Now

103

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

citicards.com

citicards.com

457 ms

citi.action

citi.action

666 ms

CitiCards_sass.css

CitiCards_sass.css

414 ms

CitiCards_sass_res.css

CitiCards_sass_res.css

1308 ms

jquery-1.7.2.js

jquery-1.7.2.js

1535 ms

jfp.branding.js

jfp.branding.js

1476 ms

jquery-ui-1.8.18.js

jquery-ui-1.8.18.js

1991 ms

ShopCookie.js

ShopCookie.js

1475 ms

amw.js

amw.js

1475 ms

AOSDMP-RF.js

AOSDMP-RF.js

1475 ms

normalize.css

normalize.css

2390 ms

jfpw.tooltip.css

jfpw.tooltip.css

1412 ms

CitiCommonMkt.js

CitiCommonMkt.js

2802 ms

vendors.top.min.js

vendors.top.min.js

3188 ms

som-banners.css

som-banners.css

3186 ms

Bootstrap.js

Bootstrap.js

5095 ms

rmegamenu.js

rmegamenu.js

4953 ms

branding_universal.js

branding_universal.js

4954 ms

vendors.bot.min.js

vendors.bot.min.js

4953 ms

mainMkt.js

mainMkt.js

5045 ms

navigation.js

navigation.js

4724 ms

style4.js

style4.js

5227 ms

target.js

target.js

2493 ms

standard

standard

2296 ms

serverComponent.php

serverComponent.php

356 ms

22b91aa67cc4638eb23533f9d1a98a6e.js

22b91aa67cc4638eb23533f9d1a98a6e.js

507 ms

42b9e8c47e0c31de3459a64782c78bbf.js

42b9e8c47e0c31de3459a64782c78bbf.js

743 ms

89932526ef3933986621bb8c03ec328a.js

89932526ef3933986621bb8c03ec328a.js

923 ms

e13ec2a18c16c2c2613289d855195fe3.js

e13ec2a18c16c2c2613289d855195fe3.js

924 ms

846967aa137d79f07363f8fac17a7b7c.js

846967aa137d79f07363f8fac17a7b7c.js

922 ms

95f6f5f72c6cb3019065a6679464d932.js

95f6f5f72c6cb3019065a6679464d932.js

1359 ms

10ce1935075d24d8d6b0c4a5482efdb0.js

10ce1935075d24d8d6b0c4a5482efdb0.js

1412 ms

0584289806b8b0ee113ca89d877d6673.js

0584289806b8b0ee113ca89d877d6673.js

1395 ms

6a97bfae240194fd3ecea689c1bc964a.js

6a97bfae240194fd3ecea689c1bc964a.js

1394 ms

d3417668cdbe3fe4889507ba3dac3eea.js

d3417668cdbe3fe4889507ba3dac3eea.js

1394 ms

fbba1b49d6dc5507a60c3a29bdfc74e7.js

fbba1b49d6dc5507a60c3a29bdfc74e7.js

1394 ms

igg

igg

444 ms

pixel

pixel

1309 ms

header_blueWave.jpg

header_blueWave.jpg

746 ms

citi_logo.png

citi_logo.png

405 ms

sprites.png

sprites.png

389 ms

browser_mess_pattern.gif

browser_mess_pattern.gif

367 ms

Red_GlobalAlert_Icon.png

Red_GlobalAlert_Icon.png

389 ms

bg_shadow_nav.png

bg_shadow_nav.png

366 ms

beacon

beacon

3635 ms

InterstateRegular.otf

InterstateRegular.otf

270 ms

preloader.gif

preloader.gif

3476 ms

content-block-separator.jpg

content-block-separator.jpg

671 ms

adchoice-ccc.png

adchoice-ccc.png

3024 ms

gr_signOn_horizontal_seperator.png

gr_signOn_horizontal_seperator.png

4425 ms

4263 ms

InterstateBold.otf

InterstateBold.otf

4296 ms

citi.action

citi.action

3018 ms

OL_Close_Btn.png

OL_Close_Btn.png

409 ms

activityi;src=6260004;type=cards0;cat=cardp0;u4=jJRSMARKETING_CitiHome;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=757950923871.2489

activityi;src=6260004;type=cards0;cat=cardp0;u4=jJRSMARKETING_CitiHome;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=757950923871.2489

1791 ms

19469

19469

1321 ms

923 ms

tc.min.js

tc.min.js

3549 ms

activity

activity

4081 ms

ld.js

ld.js

4080 ms

conversion_async.js

conversion_async.js

4479 ms

csesb

csesb

2089 ms

gpol

gpol

1685 ms

vt-70.js

vt-70.js

4065 ms

fbevents.js

fbevents.js

3744 ms

ca.html

ca.html

3732 ms

DTZ.html

DTZ.html

944 ms

1889 ms

meta

meta

1061 ms

igg

igg

1168 ms

igg

igg

1666 ms

idr.js

idr.js

5718 ms

49762

49762

1042 ms

event

event

5055 ms

425466.html

425466.html

814 ms

startseitep=plloydsbank

startseitep=plloydsbank

572 ms

570 ms

login

login

1752 ms

1750 ms

998480723620054

998480723620054

1116 ms

s67109501319937

s67109501319937

3825 ms

csesb

csesb

3342 ms

401696.gif

401696.gif

5362 ms

csesb

csesb

4047 ms

4272 ms

4355 ms

ca.html

ca.html

4385 ms

3666 ms

3995 ms

dis.aspx

dis.aspx

4265 ms

banner

banner

1531 ms

igg

igg

1264 ms

igg

igg

1263 ms

compare-button.gif

compare-button.gif

1158 ms

420356.gif

420356.gif

1908 ms

21398

21398

1908 ms

sync

sync

2028 ms

bb84-cards_lg.png

bb84-cards_lg.png

1843 ms

citi.action

citi.action

1381 ms

lightgray-md-bg-lg.jpg

lightgray-md-bg-lg.jpg

1348 ms

tr

tr

1329 ms

igg

igg

703 ms

igg

igg

733 ms

snare.js

snare.js

2262 ms

tpid=0-654da6d4-b487-43c4-8ed0-93acbaeecde8

tpid=0-654da6d4-b487-43c4-8ed0-93acbaeecde8

686 ms

blank.gif

blank.gif

1192 ms

362708.gif

362708.gif

498 ms

sync

sync

549 ms

Accessibility Review

citicards.com accessibility score

100

Accessibility Issues

Best Practices

citicards.com 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

citicards.com SEO score

91

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

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

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citicards.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 Citicards.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.

Social Sharing Optimization

citicards.com

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