Tools & Wizards About Us
cardfool.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

cardfool.com

Birthday Cards & Funny Birthday Cards, Greeting Cards and Ecards sent for you!

Page Load Speed

2.4 sec in total

First Response

220 ms

Resources Loaded

1.9 sec

Page Rendered

292 ms

cardfool.com screenshot

About Website

Visit cardfool.com now to see the best up-to-date Cardfool content for United States and also check out these interesting facts you probably never knew about cardfool.com

Send real Greeting Cards or Send Ecards Instantly for Birthday, Thank You, Anniversary, Congratulations, and more with the largest collection of One-of-a-Kind Designs! Add your own handwritten custom ...

Visit cardfool.com

Key Findings

We analyzed Cardfool.com page load time and found that the first response time was 220 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

cardfool.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

cardfool.com

220 ms

www.cardfool.com

183 ms

www.cardfool.com

463 ms

all-9ea7e862b6f8b9ae1296a49aa6fef3d1.js

127 ms

application-bdf6ed1ef7e995e8666404a541699954.css

83 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 9% of them (5 requests) were addressed to the original Cardfool.com, 15% (8 requests) were made to Www3.cardfool.com and 15% (8 requests) were made to Www2.cardfool.com. The less responsive or slowest element that took the longest time to load (679 ms) relates to the external source Www0.cardfool.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 721.4 kB (40%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cardfool.com main page is 1.8 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. 35% of websites need less resources to load. Images take 950.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 40.0 kB

  • Original 52.0 kB
  • After minification 40.9 kB
  • After compression 12.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 11.1 kB, which is 21% 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 40.0 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 113.2 kB

  • Original 950.4 kB
  • After minification 837.3 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, Cardfool needs image optimization as it can save up to 113.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 318.9 kB

  • Original 495.3 kB
  • After minification 495.0 kB
  • After compression 176.4 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 318.9 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 249.3 kB

  • Original 300.3 kB
  • After minification 298.8 kB
  • After compression 51.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. Cardfool.com needs all CSS files to be minified and compressed as it can save up to 249.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (26%)

Requests Now

47

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cardfool.com

cardfool.com

220 ms

www.cardfool.com

www.cardfool.com

183 ms

www.cardfool.com

www.cardfool.com

463 ms

all-9ea7e862b6f8b9ae1296a49aa6fef3d1.js

all-9ea7e862b6f8b9ae1296a49aa6fef3d1.js

127 ms

application-bdf6ed1ef7e995e8666404a541699954.css

application-bdf6ed1ef7e995e8666404a541699954.css

83 ms

filepicker.js

filepicker.js

307 ms

application-8a67e0bb5da62324c095bc56c13df097.js

application-8a67e0bb5da62324c095bc56c13df097.js

101 ms

getSeal

getSeal

563 ms

fbevents.js

fbevents.js

381 ms

prum.min.js

prum.min.js

83 ms

cardfool-logo-bea927d30feca7b43e64eda3c1697759.png

cardfool-logo-bea927d30feca7b43e64eda3c1697759.png

43 ms

reminder-alert.png

reminder-alert.png

214 ms

cart_link

cart_link

166 ms

magnifying-glass-40f218d6396ceee5b28fed110c0b4b5d.png

magnifying-glass-40f218d6396ceee5b28fed110c0b4b5d.png

54 ms

a.jpg

a.jpg

433 ms

social-webcam-icon-aa3474d364381985536fae69b2946c70.png

social-webcam-icon-aa3474d364381985536fae69b2946c70.png

679 ms

footer-google+-0816a2026df45107c5137bcc2a6357ed.png

footer-google+-0816a2026df45107c5137bcc2a6357ed.png

128 ms

social-facebook-icon-8992c88bdea4507324f2e22debd3e44d.png

social-facebook-icon-8992c88bdea4507324f2e22debd3e44d.png

130 ms

social-instagram-icon-b0775c3bd154519adb9409efe438f8a8.png

social-instagram-icon-b0775c3bd154519adb9409efe438f8a8.png

147 ms

social-cloud-icon-c6bebd6a99b3cc88a0e0b8dd7646b322.png

social-cloud-icon-c6bebd6a99b3cc88a0e0b8dd7646b322.png

147 ms

menu-icon-d33cbfe6ddc72e9d5b1c629af78c434b.png

menu-icon-d33cbfe6ddc72e9d5b1c629af78c434b.png

128 ms

social-computer-icon-6038d250b436cf7c6909a4bac47584f4.png

social-computer-icon-6038d250b436cf7c6909a4bac47584f4.png

129 ms

social-flickr-icon-1e0b9a2d4449b314082246668562477c.png

social-flickr-icon-1e0b9a2d4449b314082246668562477c.png

146 ms

c1.jpg

c1.jpg

338 ms

c2.jpg

c2.jpg

337 ms

b1.jpg

b1.jpg

317 ms

b2.jpg

b2.jpg

372 ms

b3.jpg

b3.jpg

377 ms

b4.jpg

b4.jpg

361 ms

digital-tip-630a38414be9eb5ce88716b530a32fa8.png

digital-tip-630a38414be9eb5ce88716b530a32fa8.png

275 ms

footer-facebook-d554528434186d94c11f878db6ce0b3c.png

footer-facebook-d554528434186d94c11f878db6ce0b3c.png

274 ms

footer-twitter-7bea5986fe3c1e8c310e7d0a16af9409.png

footer-twitter-7bea5986fe3c1e8c310e7d0a16af9409.png

274 ms

social-picasa-icon-b35e4a53c8a69ff3b91ee4fef2e67ad5.png

social-picasa-icon-b35e4a53c8a69ff3b91ee4fef2e67ad5.png

266 ms

CardFool-Thumb-6603cd0b72f3640ca70d270aadf88ed1.jpg

CardFool-Thumb-6603cd0b72f3640ca70d270aadf88ed1.jpg

305 ms

Sanchezregular-4357cc4aa2eba3cca42d9f395c1fa98c.otf

Sanchezregular-4357cc4aa2eba3cca42d9f395c1fa98c.otf

276 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

192 ms

analytics.js

analytics.js

211 ms

dbe06cd9-e293-4ab7-af7f-45f583d02fdb.js

dbe06cd9-e293-4ab7-af7f-45f583d02fdb.js

231 ms

card-expand-arrow-783cbdb2f0e631ce607c9d6c95da7621.png

card-expand-arrow-783cbdb2f0e631ce607c9d6c95da7621.png

132 ms

card-inside-peek-4cc7756ced5d28dac39c225c54ee99e5.png

card-inside-peek-4cc7756ced5d28dac39c225c54ee99e5.png

128 ms

customize-shelf-458a6d2f54fd7c40beff60609bccacf1.png

customize-shelf-458a6d2f54fd7c40beff60609bccacf1.png

139 ms

card-inside-left-64ace466fc714912050f7cc7139eed23.png

card-inside-left-64ace466fc714912050f7cc7139eed23.png

151 ms

6563.js

6563.js

222 ms

173 ms

194 ms

my_reminders.json

my_reminders.json

157 ms

ui-bg_flat_75_ffffff_40x100-8459fb47ea4455006f01b798d70291be.png

ui-bg_flat_75_ffffff_40x100-8459fb47ea4455006f01b798d70291be.png

48 ms

87 ms

collect

collect

28 ms

collect

collect

70 ms

collect

collect

46 ms

a.gif

a.gif

98 ms

ga-audiences

ga-audiences

35 ms

Accessibility Review

cardfool.com accessibility score

63

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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 IDs 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

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>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

cardfool.com best practices score

75

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

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

cardfool.com SEO score

81

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    UTF-8

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

cardfool.com

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