Tools & Wizards About Us
agmobile.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

agmobile.com

Greeting Cards, Ecards & More | American Greetings

Page Load Speed

1.2 sec in total

First Response

38 ms

Resources Loaded

934 ms

Page Rendered

264 ms

agmobile.com screenshot

About Website

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

Make Meaningful Connections With American Greetings Selection Of Online Greeting Cards Including Ecards, SmashUps™, Creatacards, Digital Gifts And More!

Visit agmobile.com

Key Findings

We analyzed Agmobile.com page load time and found that the first response time was 38 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

agmobile.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.404

25/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

agmobile.com

38 ms

www.americangreetings.com

412 ms

jquery-3.2.1.min.js

102 ms

js-offcanvas.css

95 ms

bootstrap-accessibility.min.css

69 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Agmobile.com, 91% (62 requests) were made to Ak.imgag.com and 3% (2 requests) were made to Cdn.dynamicyield.com. The less responsive or slowest element that took the longest time to load (412 ms) relates to the external source Americangreetings.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 520.3 kB (18%)

Content Size

2.9 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Agmobile.com main page is 2.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 194.7 kB

  • Original 207.2 kB
  • After minification 73.0 kB
  • After compression 12.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 134.2 kB, which is 65% 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 194.7 kB or 94% of the original size.

Image Optimization

-6%

Potential reduce by 131.2 kB

  • Original 2.3 MB
  • After minification 2.2 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. Agmobile images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 186.5 kB

  • Original 298.9 kB
  • After minification 292.5 kB
  • After compression 112.4 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 186.5 kB or 62% of the original size.

CSS Optimization

-9%

Potential reduce by 7.9 kB

  • Original 84.2 kB
  • After minification 84.2 kB
  • After compression 76.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. Agmobile.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

62

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

agmobile.com

agmobile.com

38 ms

www.americangreetings.com

www.americangreetings.com

412 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

102 ms

js-offcanvas.css

js-offcanvas.css

95 ms

bootstrap-accessibility.min.css

bootstrap-accessibility.min.css

69 ms

americangreetings-styles.css

americangreetings-styles.css

82 ms

bootstrap.min.js

bootstrap.min.js

75 ms

modernizr-custom.min.js

modernizr-custom.min.js

74 ms

js-offcanvas.pkgd.min.js

js-offcanvas.pkgd.min.js

80 ms

bootstrap-accessibility.min.js

bootstrap-accessibility.min.js

83 ms

en-2.1.19.min.js

en-2.1.19.min.js

87 ms

datepicker-2.1.19.min.js

datepicker-2.1.19.min.js

100 ms

errorHandler.js

errorHandler.js

88 ms

api_dynamic.js

api_dynamic.js

97 ms

api_static.js

api_static.js

174 ms

searchbox.js

searchbox.js

90 ms

searchEventToDY.js

searchEventToDY.js

91 ms

passwordForm.js

passwordForm.js

96 ms

signInAjax.js

signInAjax.js

172 ms

signInSignOut.js

signInSignOut.js

188 ms

reminderWidget.js

reminderWidget.js

171 ms

headerItemNavigation.js

headerItemNavigation.js

191 ms

seoMarkup.js

seoMarkup.js

186 ms

carouselBanner.js

carouselBanner.js

185 ms

multi-line-ellipsis.js

multi-line-ellipsis.js

215 ms

addToCart.js

addToCart.js

215 ms

jquery.forms.min.js

jquery.forms.min.js

188 ms

productDrawer.js

productDrawer.js

188 ms

featuredProductTile.js

featuredProductTile.js

211 ms

carousel-swipe.js

carousel-swipe.js

210 ms

productCarousel.js

productCarousel.js

209 ms

capturePermission.js

capturePermission.js

209 ms

accessibility.js

accessibility.js

209 ms

tileUtils.js

tileUtils.js

210 ms

inert-polyfill.min.js

inert-polyfill.min.js

209 ms

linkItemDropdown.js

linkItemDropdown.js

210 ms

polyfills.js

polyfills.js

210 ms

polyfill.min.js

polyfill.min.js

302 ms

search.png

search.png

60 ms

image.png

image.png

56 ms

image.jpg

image.jpg

56 ms

image.jpg

image.jpg

58 ms

image.jpg

image.jpg

57 ms

image.jpg

image.jpg

60 ms

image.jpg

image.jpg

60 ms

image.jpg

image.jpg

56 ms

image.jpg

image.jpg

58 ms

image.jpg

image.jpg

57 ms

image.png

image.png

61 ms

image.jpg

image.jpg

59 ms

image.jpg

image.jpg

163 ms

image.gif

image.gif

112 ms

image.jpg

image.jpg

111 ms

image.png

image.png

60 ms

image.png

image.png

61 ms

image.png

image.png

61 ms

image.png

image.png

62 ms

image.png

image.png

60 ms

image.png

image.png

93 ms

reminders.png

reminders.png

91 ms

dropdown-indicators.png

dropdown-indicators.png

71 ms

peak-nav.jpg

peak-nav.jpg

74 ms

utag.js

utag.js

134 ms

34e0e4c0-c294-49bb-9a8e-1b2cafd54e32.woff

34e0e4c0-c294-49bb-9a8e-1b2cafd54e32.woff

51 ms

439c5962-f9fe-4eaf-a1f6-f41d42edba75.woff

439c5962-f9fe-4eaf-a1f6-f41d42edba75.woff

75 ms

050b1948-f226-4d20-a65a-15d8ed031222.woff

050b1948-f226-4d20-a65a-15d8ed031222.woff

53 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

53 ms

mtiFontTrackingCode.js

mtiFontTrackingCode.js

25 ms

Accessibility Review

agmobile.com accessibility score

91

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 input fields do not have accessible names

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

Best Practices

agmobile.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

agmobile.com SEO score

89

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

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

agmobile.com

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