Tools & Wizards About Us
lecards.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lecards.com

Print Shop Online | Same Day Stickers, Business Cards & More

Page Load Speed

4 sec in total

First Response

71 ms

Resources Loaded

3.4 sec

Page Rendered

524 ms

lecards.com screenshot

About Website

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

We are a print shop online that can print foil stickers, custom business cards, postcards, flyers, menus, banners, and trade show printing. 323-744-0338

Visit lecards.com

Key Findings

We analyzed Lecards.com page load time and found that the first response time was 71 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

lecards.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value26.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.6 s

0/100

25%

SI (Speed Index)

Value26.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value40.4 s

0/100

10%

Network Requests Diagram

lecards.com

71 ms

www.lecards.com

410 ms

efad30668a2be40cf4475b8e24f21a5b.min.css

422 ms

styles-l.min.css

50 ms

font-awesome.min.css

36 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 58% of them (31 requests) were addressed to the original Lecards.com, 8% (4 requests) were made to Googletagmanager.com and 6% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (712 ms) belongs to the original domain Lecards.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 403.7 kB (7%)

Content Size

6.1 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lecards.com main page is 6.1 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. 65% of websites need less resources to load. Javascripts take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 148.7 kB

  • Original 180.2 kB
  • After minification 170.6 kB
  • After compression 31.5 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 148.7 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 50.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Le Cards images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 35.2 kB

  • Original 4.4 MB
  • After minification 4.4 MB
  • After compression 4.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-84%

Potential reduce by 168.9 kB

  • Original 202.0 kB
  • After minification 33.1 kB
  • After compression 33.1 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. Lecards.com needs all CSS files to be minified and compressed as it can save up to 168.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

47

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Le 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 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lecards.com

lecards.com

71 ms

www.lecards.com

www.lecards.com

410 ms

efad30668a2be40cf4475b8e24f21a5b.min.css

efad30668a2be40cf4475b8e24f21a5b.min.css

422 ms

styles-l.min.css

styles-l.min.css

50 ms

font-awesome.min.css

font-awesome.min.css

36 ms

ed05e7402941f902f457c038b81dc909.min.js

ed05e7402941f902f457c038b81dc909.min.js

131 ms

js

js

67 ms

js

js

114 ms

00e74319d2329ea04df9579e8.js

00e74319d2329ea04df9579e8.js

160 ms

svg-sprite.min.js

svg-sprite.min.js

38 ms

fbevents.js

fbevents.js

250 ms

events.js

events.js

310 ms

logo-new-2017-color.png

logo-new-2017-color.png

319 ms

phone.svg

phone.svg

246 ms

clock.svg

clock.svg

247 ms

paper-stickers.jpg

paper-stickers.jpg

248 ms

foil-stickers.jpg

foil-stickers.jpg

670 ms

vinyl-stickers.jpg

vinyl-stickers.jpg

712 ms

roll-labels.jpg

roll-labels.jpg

669 ms

die-cut-stickers.jpg

die-cut-stickers.jpg

669 ms

home-image1.jpg

home-image1.jpg

319 ms

telephone-call.png

telephone-call.png

415 ms

email-ic.png

email-ic.png

414 ms

pin.png

pin.png

415 ms

facebook.png

facebook.png

416 ms

google-plus.png

google-plus.png

416 ms

instagram.png

instagram.png

669 ms

yelp-logo.png

yelp-logo.png

416 ms

payments1.png

payments1.png

417 ms

js-translation.json

js-translation.json

574 ms

248 ms

146 ms

js

js

131 ms

analytics.js

analytics.js

125 ms

246 ms

Roboto-700.woff

Roboto-700.woff

630 ms

Roboto-400.woff

Roboto-400.woff

682 ms

main.MTZmOTQwMTEyMA.js

main.MTZmOTQwMTEyMA.js

97 ms

49 ms

collect

collect

21 ms

sticker-banner.jpg

sticker-banner.jpg

656 ms

43 ms

hotjar-2250468.js

hotjar-2250468.js

107 ms

v2.zopim.com

v2.zopim.com

80 ms

embed.js

embed.js

43 ms

asset_composer.js

asset_composer.js

41 ms

modules.db8890ba82a7e392473f.js

modules.db8890ba82a7e392473f.js

14 ms

collect

collect

48 ms

js

js

62 ms

loader-1.gif

loader-1.gif

64 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

266 ms

whitebh.jpg

whitebh.jpg

444 ms

print.min.css

print.min.css

256 ms

Accessibility Review

lecards.com accessibility score

84

Accessibility Issues

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-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

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

lecards.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

lecards.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

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

lecards.com

Open Graph description is not detected on the main page of Le Cards. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: