Tools & Wizards About Us
quillcards.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

quillcards.com

Beautiful, Distinctive Ecards

Page Load Speed

1.7 sec in total

First Response

466 ms

Resources Loaded

1 sec

Page Rendered

165 ms

quillcards.com screenshot

About Website

Visit quillcards.com now to see the best up-to-date Quillcards content and also check out these interesting facts you probably never knew about quillcards.com

Quillcards - beautiful, distinctive ecards featuring photographs and quotations - arranged in easy to use themes.

Visit quillcards.com

Key Findings

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

Performance Metrics

quillcards.com performance score

0

Network Requests Diagram

quillcards.com

466 ms

combo

14 ms

css

26 ms

application.css

96 ms

jquery.min.js

6 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 19% of them (9 requests) were addressed to the original Quillcards.com, 33% (16 requests) were made to Images.quillcards.com and 17% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (466 ms) belongs to the original domain Quillcards.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.0 kB (33%)

Content Size

449.2 kB

After Optimization

303.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 15.2 kB

  • Original 20.4 kB
  • After minification 17.5 kB
  • After compression 5.2 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 2.9 kB, which is 14% 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 15.2 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 19.1 kB

  • Original 269.5 kB
  • After minification 250.4 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. Quillcards images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 89.8 kB

  • Original 133.3 kB
  • After minification 98.8 kB
  • After compression 43.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 89.8 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 21.9 kB

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

Requests Breakdown

Number of requests can be reduced by 14 (31%)

Requests Now

45

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

quillcards.com

quillcards.com

466 ms

combo

combo

14 ms

css

css

26 ms

application.css

application.css

96 ms

jquery.min.js

jquery.min.js

6 ms

jquery-ui.min.js

jquery-ui.min.js

11 ms

application.js

application.js

255 ms

js

js

8 ms

01209.jpg

01209.jpg

108 ms

quillcards-logo.png

quillcards-logo.png

107 ms

quillcards-header-logged-out.png

quillcards-header-logged-out.png

208 ms

blue-arrow.png

blue-arrow.png

167 ms

paypal-quillcards-45.png

paypal-quillcards-45.png

178 ms

Q0097.jpg

Q0097.jpg

104 ms

00233.jpg

00233.jpg

118 ms

03080.jpg

03080.jpg

120 ms

01243.jpg

01243.jpg

138 ms

Q0102.jpg

Q0102.jpg

106 ms

00935.jpg

00935.jpg

139 ms

03026.jpg

03026.jpg

154 ms

03034.jpg

03034.jpg

152 ms

01057.jpg

01057.jpg

176 ms

00326.jpg

00326.jpg

164 ms

01315.jpg

01315.jpg

194 ms

00342.jpg

00342.jpg

165 ms

00436.jpg

00436.jpg

233 ms

00237.jpg

00237.jpg

215 ms

00937.jpg

00937.jpg

206 ms

plusone.js

plusone.js

69 ms

IhBhtOi02NLuvxWW4RuNVg.ttf

IhBhtOi02NLuvxWW4RuNVg.ttf

64 ms

ga.js

ga.js

25 ms

__utm.gif

__utm.gif

22 ms

overlay.png

overlay.png

107 ms

controls.png

controls.png

168 ms

like.php

like.php

159 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

23 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

fastbutton

fastbutton

88 ms

postmessageRelay

postmessageRelay

52 ms

in.php

in.php

136 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

10 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

30 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

22 ms

rpc:shindig_random.js

rpc:shindig_random.js

46 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

43 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

34 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

SEO Factors

quillcards.com SEO score

0

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

quillcards.com

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