Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

cardsinthepost.com

Postcards - Cards in the Post: Make a postcard online and we'll mail it for you

Page Load Speed

1.8 sec in total

First Response

264 ms

Resources Loaded

1.4 sec

Page Rendered

139 ms

cardsinthepost.com screenshot

About Website

Click here to check amazing Cards In The Post content for United States. Otherwise, check out these important facts you probably never knew about cardsinthepost.com

The easiest quickest way to make your pictures into postcards that we print and mail for you. Drag and drop any pic you like. Works on anything - mobile, tablet or desktop - it's the most flexible way...

Visit cardsinthepost.com

Key Findings

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

Performance Metrics

cardsinthepost.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value350 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

cardsinthepost.com

264 ms

postcard

225 ms

css

29 ms

compiled_cardscore.css

82 ms

compiled_cardsinterface.css

156 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 34% of them (11 requests) were addressed to the original Cardsinthepost.com, 19% (6 requests) were made to Static.xx.fbcdn.net and 9% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (264 ms) belongs to the original domain Cardsinthepost.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.5 kB (68%)

Content Size

190.9 kB

After Optimization

60.4 kB

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

HTML Optimization

-79%

Potential reduce by 44.2 kB

  • Original 56.1 kB
  • After minification 49.7 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 11% 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 44.2 kB or 79% of the original size.

Image Optimization

-29%

Potential reduce by 2.1 kB

  • Original 7.2 kB
  • After minification 5.1 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, Cards In The Post needs image optimization as it can save up to 2.1 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 64.0 kB

  • Original 101.5 kB
  • After minification 101.5 kB
  • After compression 37.5 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 64.0 kB or 63% of the original size.

CSS Optimization

-77%

Potential reduce by 20.2 kB

  • Original 26.1 kB
  • After minification 26.1 kB
  • After compression 5.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. Cardsinthepost.com needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (55%)

Requests Now

29

After Optimization

13

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

Accessibility Review

cardsinthepost.com accessibility score

56

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

SEO Factors

cardsinthepost.com SEO score

83

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

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

    N/A

  • Encoding

    ISO-8859-1

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

Open Graph description is not detected on the main page of Cards In The Post. 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: