3.7 sec in total
103 ms
2.9 sec
689 ms
Welcome to card.ly homepage info - get ready to check Card best content right away, or after learning these important things about card.ly
Send a beautiful, handwritten card to a loved one without lifting a pen. Cards posted same day! Free shipping within the UK, US, Australia, Canada & Europe.
Visit card.lyWe analyzed Card.ly page load time and found that the first response time was 103 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
card.ly performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value9.0 s
1/100
25%
Value11.2 s
5/100
10%
Value1,650 ms
11/100
30%
Value0.008
100/100
15%
Value12.7 s
13/100
10%
103 ms
75 ms
73 ms
85 ms
32 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Card.ly, 13% (8 requests) were made to Sdk.engage.co and 13% (8 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (623 ms) relates to the external source Wapi.engage.co.
Page size can be reduced by 276.4 kB (33%)
830.0 kB
553.6 kB
In fact, the total size of Card.ly main page is 830.0 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. 70% of websites need less resources to load. Images take 499.2 kB which makes up the majority of the site volume.
Potential reduce by 89.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 89.9 kB or 83% of the original size.
Potential reduce by 74.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, Card needs image optimization as it can save up to 74.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 112.2 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 112.2 kB or 51% of the original size.
Potential reduce by 19 B
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. Card.ly has all CSS files already compressed.
Number of requests can be reduced by 15 (38%)
40
25
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.engage.co
103 ms
t75lIcVyNcq4B-nAOdZ16X3R3xIK9m_Z453kbYpg5QjfeCqffFHN4UJLFRbh52jhWD9XFDwujDqaZQsKw2gyZRqaZAjaZejXFyTmiaiaOcm0ZhB1ZPoRdkU8dciyZh90jhvCdeNRjAUGdaFXOem0ZhB1ZAFzO1FUiABkZWF3jAF8OcFzdP37Ocm0ZhB1ZAFzO1FUiABkZWF3jAF8OcFzdPJ4Z1mXiW4yOWgXJ6Z8iW4zSeI7fbKemsMMeMw6MKG4fJFmIMMj2PMfH6qJyB9bMg6IJMJ7fbKBmsMMeMt6MKG4fVN9IMMjgPMfH6qJ6B9bMg6VJMJ7fbKgmsMMeMS6MKG4fJ4mIMMjIPMfH6qJyu9bMg6JJMJ7fbKJmsMMegJ6MKG4fH8oIMIjMkMfH6GJttjgIMIj2PMfH6qJ71qbMs6IJMJ7f6Rqy6IbMs65JMJ7fbKGpsMgeMS6MKGHf5AeMsMgegI6MTMg8nD3lM9.js
75 ms
css
73 ms
jquery-2.1.3.min.js
85 ms
sdk.js
32 ms
82 ms
sdk.js
53 ms
6d4a
218 ms
common-83bc84ae3859fda84f05-min.js
84 ms
commerce-7e265c35baa8a39650b8-min.js
45 ms
commerce-7f4130fee43d9b486ac93410db2112d3-min.css
23 ms
site.css
76 ms
w.js
213 ms
ga.js
212 ms
social-accounts.svg
159 ms
152 ms
Nd_-hec2f5jv3dYBToySYJsg39ROcch7WZ7AXoUnUybffHQQggMdeMI6MK6f5Mb.eot
100 ms
QY8qJq8sckvkSCu_2enbuvCFbQjoHOhimjiDbi_cQL9ffHWQggMdeMI6MK6f5MS.eot
100 ms
lxSDBui7bO2LQ_Qi0_JViSymT3YVH8-Rw6FpmDwy_gMff5WcggMdeMI6MK6f5Mb.eot
573 ms
2mSJCXYSaPtYmM21xopNF3I8Nm3a01Thy56PNO0mbjqff4egggMdeMI6MK6f5MS.eot
574 ms
clickstream.min.js
93 ms
__utm.gif
484 ms
widgetConfig
623 ms
Engage+backdrop+16.jpg
517 ms
RecordHit
343 ms
pinterest-6c61bef81af92ee69eae-min.js
263 ms
collect
311 ms
270 ms
desktop-typical.png
294 ms
270 ms
265 ms
storage.luckyorange.net
337 ms
qRCcMDLZ7OQ0qhCTYuW6y4o4Szn1tqLE9zO7LagzxUJffHLQggMdeMI6MK6f5Mt.eot
77 ms
kPZGF5dSh6FlkFkjdVhsjyenb-MS-V-nv1dVhbB9_-CffHRQggMdeMI6MK6f5gI.eot
75 ms
gKFXYFzss5AfUfKuO09OX7kR3HCgPE53IwL1ZGtnLxMffHdQggMdeMI6MK6f5MX.eot
76 ms
nIJRb5hi3L3e_XEXJMhVU6wdx_YgcMOEAGMPSRvMlUMffHVQggMdeMI6MK6f5Mw.eot
77 ms
HqoxoWM-01KgvwTYb0qEmiWZ4r-u27liHlY346syoy9ff4AgggMdeMI6MK6f5Mt.eot
315 ms
hbRMR8mBs642rllO17rGayKa1qiDB6Ws7Gi141_OS-Sff4HgggMdeMI6MK6f5gI.eot
316 ms
zjD7hVDuOvsZ0KEg3lKxu0WX8f51r7OWfU8NHoTWSbvff45gggMdeMI6MK6f5MX.eot
318 ms
qsFef_iXgIj8MvJYuiHxfeJQ95f_oVBUBt44rfpB6_Cff4fgggMdeMI6MK6f5Mv.eot
315 ms
azzJB7bBLWco6TXxoWJgZVLFWVYqUfe7JbgzrtWp_69ff4KgggMdeMI6MK6f5gJ.eot
419 ms
MqFVJNWkzPkzkNMFrntMD4wTlsW4SXqBFvy8AeQRfiMff4-gggMdeMI6MK6f5Mw.eot
525 ms
Tvrr9vQPnCW1SQ301tWnkpKGoJnfC1Jr4GBMgyOnLY9ffJrgggMdeMI6MK6f5M9.eot
439 ms
oSPTxXbyPXJvUWVjl9VeKHcQWcRdJYLp26FTZZagNDJff4pgggMdeMI6MK6f5M6.eot
437 ms
track
261 ms
toolbar.js
53 ms
toolbar.css
54 ms
getUsers
270 ms
user.png
142 ms
track
278 ms
close.png
136 ms
RightArrow.png
159 ms
back.png
161 ms
settings.luckyorange.net
132 ms
7f195fc60e7b32288cc1596c288a98acDanny.jpg
202 ms
user-status
147 ms
large_1436288610largechiragpancholi_cropped.jpg
181 ms
e44acf35adf0a29ea63e6842222db62bLiefLarson100.jpg
196 ms
f409c175e7a7cbf1e5dfe118ca161118wade_pic.png
215 ms
social-accounts.svg
14 ms
card.ly accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
card.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
card.ly SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Card.ly 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 Card.ly 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.
card.ly
Open Graph data is detected on the main page of Card. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: