Tools & Wizards About Us
freecard.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

freecard.com

Business Opportunity Free Card Business Card Display Advertising.

Page Load Speed

974 ms in total

First Response

155 ms

Resources Loaded

722 ms

Page Rendered

97 ms

freecard.com screenshot

About Website

Click here to check amazing Free Card content. Otherwise, check out these important facts you probably never knew about freecard.com

Free Card. Business card displays. Home based business opportunity sending freecards, printing and distributing free cards.

Visit freecard.com

Key Findings

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

Performance Metrics

freecard.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

99/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

freecard.com

155 ms

styles.css

69 ms

ga.js

12 ms

button1.gif

69 ms

skybg.gif

183 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 90% of them (18 requests) were addressed to the original Freecard.com, 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (419 ms) belongs to the original domain Freecard.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.0 kB (28%)

Content Size

32.3 kB

After Optimization

23.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Freecard.com main page is 32.3 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. 20% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 8.2 kB

  • Original 11.8 kB
  • After minification 10.3 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.4 kB, which is 12% 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 8.2 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 636 B
  • After minification 636 B

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. Free Card images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-28%

Potential reduce by 757 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 1.9 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. Freecard.com needs all CSS files to be minified and compressed as it can save up to 757 B or 28% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Free Card. According to our analytics all requests are already optimized.

Network Requests Diagram

freecard.com

freecard.com

155 ms

styles.css

styles.css

69 ms

ga.js

ga.js

12 ms

button1.gif

button1.gif

69 ms

skybg.gif

skybg.gif

183 ms

freecard_logo.gif

freecard_logo.gif

128 ms

support.gif

support.gif

129 ms

leftimage.jpg

leftimage.jpg

301 ms

home-based-business-opportu.gif

home-based-business-opportu.gif

419 ms

bottombg.gif

bottombg.gif

132 ms

AroundWorld.gif

AroundWorld.gif

192 ms

FAQ.gif

FAQ.gif

193 ms

Business_Card_Advertising_O.gif

Business_Card_Advertising_O.gif

199 ms

About_Us.gif

About_Us.gif

245 ms

Contact_Free_Card.gif

Contact_Free_Card.gif

255 ms

testimonials.gif

testimonials.gif

317 ms

lv.jpg

lv.jpg

316 ms

cs-or-234x16.gif

cs-or-234x16.gif

310 ms

__utm.gif

__utm.gif

13 ms

noprint.css

noprint.css

67 ms

Accessibility Review

freecard.com accessibility score

53

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

<object> elements do not have alternate text

Best Practices

freecard.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

freecard.com SEO score

62

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

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freecard.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Freecard.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

freecard.com

Open Graph description is not detected on the main page of Free Card. 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: