3.1 sec in total
260 ms
2.6 sec
269 ms
Click here to check amazing Greeting Card Universe Resultspage content for Japan. Otherwise, check out these important facts you probably never knew about greetingcarduniverse.resultspage.com
Visit greetingcarduniverse.resultspage.comWe analyzed Greetingcarduniverse.resultspage.com page load time and found that the first response time was 260 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
greetingcarduniverse.resultspage.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value4.6 s
35/100
25%
Value6.5 s
39/100
10%
Value580 ms
51/100
30%
Value0.118
85/100
15%
Value10.5 s
23/100
10%
260 ms
154 ms
295 ms
155 ms
155 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Greetingcarduniverse.resultspage.com, 70% (81 requests) were made to Greetingcarduniverse.com and 8% (9 requests) were made to Nsg.symantec.com. The less responsive or slowest element that took the longest time to load (852 ms) relates to the external source B.sli-spark.com.
Page size can be reduced by 559.6 kB (61%)
917.9 kB
358.3 kB
In fact, the total size of Greetingcarduniverse.resultspage.com main page is 917.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. 50% of websites need less resources to load. Javascripts take 649.6 kB which makes up the majority of the site volume.
Potential reduce by 54.3 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 54.3 kB or 78% of the original size.
Potential reduce by 23.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, Greeting Card Universe Resultspage needs image optimization as it can save up to 23.1 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 416.0 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 416.0 kB or 64% of the original size.
Potential reduce by 66.4 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. Greetingcarduniverse.resultspage.com needs all CSS files to be minified and compressed as it can save up to 66.4 kB or 77% of the original size.
Number of requests can be reduced by 75 (67%)
112
37
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greeting Card Universe Resultspage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
greetingcarduniverse.resultspage.com
260 ms
dodger.js
154 ms
gcu.css
295 ms
gcu_header.css
155 ms
gcu_cat_menu.css
155 ms
jquery-1.9.1.min.js
35 ms
jquery-migrate-1.2.1.js
34 ms
prototype.js
444 ms
scriptaculous.js
154 ms
highslide-full.min.js
405 ms
highslide-with-html.js
439 ms
easing_equations.js
223 ms
highslide.css
224 ms
gcu_highslide.css
314 ms
overlib.js
440 ms
winpop6.css
365 ms
winpop6.js
366 ms
gcu_menu.js
437 ms
feedback.js
437 ms
feedback.css
473 ms
system1.js
505 ms
prods.css
507 ms
sli_styles.css
112 ms
sli-rac.1.6.css
11 ms
sli-rac.css
141 ms
ualib.js
489 ms
entities.js
490 ms
gcu_header.js
492 ms
placeholder.js
526 ms
subscribe.css
556 ms
ualib.js
558 ms
subscribe.js
556 ms
popin.css
558 ms
popin.js
559 ms
prev.js
592 ms
prev.css
626 ms
avmws_1011221.js
598 ms
gjs.aspx
17 ms
sli-rac.config.js
103 ms
builder.js
190 ms
effects.js
257 ms
dragdrop.js
188 ms
controls.js
221 ms
slider.js
252 ms
sound.js
261 ms
sli_logo_2014.png
40 ms
AltSealInfo.aspx
39 ms
gcu_logo_dec_2010.gif
158 ms
search_cards_dec_2010.gif
147 ms
2016_march_20_0318.png
249 ms
2014_nov_bottom3.png
149 ms
prevHeader.png
146 ms
happy_shoppers_dec_2010.gif
147 ms
reseller-ratings.png
163 ms
bbbaplus.png
164 ms
satisfaction_details_dec_2010.gif
247 ms
faq_details_dec_2010.gif
167 ms
Footer-Icon-Facebook.png
236 ms
Footer-Icon-Twitter.png
236 ms
Footer-Icon-Pinterest.png
237 ms
Footer-Icon-GooglePlus.png
237 ms
Footer-Logo-ResellerRating.gif
305 ms
Footer-Logo-BBB.gif
304 ms
Footer-Logo-GoDaddy.gif
305 ms
Footer-Logo-Truste.gif
317 ms
Footer-Logo-CreditCards.gif
411 ms
dc.js
32 ms
j.php
19 ms
all.js
276 ms
v.gif
69 ms
faq_image1_details_dec_2012.png
137 ms
faq_image2_details_dec_2012.png
195 ms
faq_image3_details_dec_2012.png
194 ms
faq_image4_details_dec_2012.png
196 ms
faq_image5_details_dec_2012.png
232 ms
faq_image6_details_dec_2012.png
232 ms
faq_image7_details_dec_2012.png
318 ms
faq_image8_details_dec_2012.png
318 ms
faq_image9_details_dec_2012.png
318 ms
faq_image10_details_dec_2012.png
311 ms
Footer-Phone-Icon.png
261 ms
Footer-FAQ-Icon.png
259 ms
Footer-Email-Icon.png
323 ms
Footer-Chat-Icon.png
321 ms
Footer-Savings-Icon.png
323 ms
107 ms
js
107 ms
spx
102 ms
sli-spark.js
852 ms
163 ms
rollover.core.js
13 ms
gtmp_compiled_9-hatpZX8VY.js
104 ms
195 ms
191 ms
xd_arbiter.php
239 ms
xd_arbiter.php
437 ms
ii.aspx
32 ms
AltSealInfo.aspx
22 ms
AltSeal.aspx
18 ms
dot.gif
6 ms
AltSealInfo.aspx
26 ms
b.png
149 ms
sli-rac.stub.1.6.js
72 ms
ping
124 ms
rounded-white.png
72 ms
green_x_dec_2010.gif
75 ms
smiley_horrible_24x24.jpg
78 ms
smiley_bad_24x24.jpg
76 ms
smiley_average_24x24.jpg
79 ms
smiley_good_24x24.jpg
79 ms
smiley_excellent_24x24.jpg
117 ms
send.jpg
130 ms
feedback.gif
220 ms
loader.white.gif
149 ms
Dynamic.aspx
16 ms
greetingcarduniverse.resultspage.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greetingcarduniverse.resultspage.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
greetingcarduniverse.resultspage.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greetingcarduniverse.resultspage.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 Greetingcarduniverse.resultspage.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.
greetingcarduniverse.resultspage.com
Open Graph description is not detected on the main page of Greeting Card Universe Resultspage. 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: