Tools & Wizards About Us
awesomemerchandise.com screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

awesomemerchandise.com

Print.inc - Awesome Merchandise

Page Load Speed

3.7 sec in total

First Response

492 ms

Resources Loaded

3 sec

Page Rendered

252 ms

awesomemerchandise.com screenshot

About Website

Welcome to awesomemerchandise.com homepage info - get ready to check Awesome Merchandise best content for United States right away, or after learning these important things about awesomemerchandise.com

Let’s create something Awesome! Custom printed T-Shirts, Stickers, Badges and more, make hundreds of custom items with Awesome Merchandise.

Visit awesomemerchandise.com

Key Findings

We analyzed Awesomemerchandise.com page load time and found that the first response time was 492 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

awesomemerchandise.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value6,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.167

1/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

www.awesomemerchandise.com

492 ms

roundtrip.js

19 ms

sc.environment.ssp

96 ms

en_GB.js

69 ms

Libraries-0150a4f9322d.js

144 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 35% of them (29 requests) were addressed to the original Awesomemerchandise.com, 12% (10 requests) were made to Cdn.bronto.com and 6% (5 requests) were made to 3031590039.log.optimizely.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Assets.zendesk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (62%)

Content Size

2.7 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Awesomemerchandise.com main page is 2.7 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. 80% 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. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 104.4 kB

  • Original 117.9 kB
  • After minification 77.8 kB
  • After compression 13.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 40.1 kB, which is 34% 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 104.4 kB or 89% of the original size.

Image Optimization

-5%

Potential reduce by 21.5 kB

  • Original 462.0 kB
  • After minification 440.5 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. Awesome Merchandise images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.4 MB

  • Original 1.9 MB
  • After minification 1.9 MB
  • After compression 539.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.4 MB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 221.1 kB

  • Original 260.3 kB
  • After minification 242.4 kB
  • After compression 39.2 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. Awesomemerchandise.com needs all CSS files to be minified and compressed as it can save up to 221.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (49%)

Requests Now

75

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.awesomemerchandise.com

www.awesomemerchandise.com

492 ms

roundtrip.js

roundtrip.js

19 ms

sc.environment.ssp

sc.environment.ssp

96 ms

en_GB.js

en_GB.js

69 ms

Libraries-0150a4f9322d.js

Libraries-0150a4f9322d.js

144 ms

Templates-01506217bb2c.js

Templates-01506217bb2c.js

63 ms

Application-0150a50d2f10.js

Application-0150a50d2f10.js

181 ms

sc.user.environment.ssp

sc.user.environment.ssp

460 ms

jxu6nwm.js

jxu6nwm.js

235 ms

Styles-0150a781b0d7.css

Styles-0150a781b0d7.css

72 ms

checkout.awesomemerchandise.com

checkout.awesomemerchandise.com

499 ms

d

d

330 ms

zenbox.css

zenbox.css

98 ms

page.ss

page.ss

101 ms

configure.js

configure.js

117 ms

awesomecolors.ss

awesomecolors.ss

256 ms

gtm.js

gtm.js

49 ms

page.ss

page.ss

159 ms

live-order.ss

live-order.ss

1038 ms

page_not_found.jsp

page_not_found.jsp

140 ms

3031590039.js

3031590039.js

274 ms

ga.js

ga.js

58 ms

main.js

main.js

182 ms

slider.ss

slider.ss

118 ms

banner.ss

banner.ss

120 ms

i.js

i.js

59 ms

37f30bedf8868c72864f67495f8c2d550706d594.2.js

37f30bedf8868c72864f67495f8c2d550706d594.2.js

60 ms

top-band.png

top-band.png

76 ms

awesome-icons.png

awesome-icons.png

49 ms

cart-icon.png

cart-icon.png

48 ms

bg-main-banners.jpg

bg-main-banners.jpg

108 ms

main-banners-set.png

main-banners-set.png

293 ms

bottom-band.jpg

bottom-band.jpg

107 ms

icon-subscription.jpg

icon-subscription.jpg

145 ms

social-icons-footer.jpg

social-icons-footer.jpg

144 ms

__utm.gif

__utm.gif

23 ms

BKEVq1AAAA==

BKEVq1AAAA==

14 ms

HVSDRfVqSETalGbOvhSl3rUx48G+BNAQxrRWFwPpAlNJQvNCKa5OBmCh1Ba4CWMlrSiNW1oSzva04GOdKIzXehKN7qLBz0lO+FE0JtI+tCXfkQRTX8GMJBBDGYIQxnGcEYQw0hiGUUco4kngUTGMJZxjGcCE5nEZKYwlWlUHVX1eAYzmcVs5lTi9ipWs4a1JFXg+2a2sJVtbK8kAUc4yjHJbUb5LPwFOavBzA==

HVSDRfVqSETalGbOvhSl3rUx48G+BNAQxrRWFwPpAlNJQvNCKa5OBmCh1Ba4CWMlrSiNW1oSzva04GOdKIzXehKN7qLBz0lO+FE0JtI+tCXfkQRTX8GMJBBDGYIQxnGcEYQw0hiGUUco4kngUTGMJZxjGcCE5nEZKYwlWlUHVX1eAYzmcVs5lTi9ipWs4a1JFXg+2a2sJVtbK8kAUc4yjHJbUb5LPwFOavBzA==

13 ms

90v+CT8yqxc=

90v+CT8yqxc=

14 ms

HVSDRfVqSETalGbOvhSl3rUx48G+BNAQxrRWFwPpAlNJQvNCKa5OBmCh1Ba4CWMlrSiNW1oSzva04GOdKIzXehKN7qLBz0lO+FE0JtI+tCXfkQRTX8GMJBBDGYIQxnGcEYQw0hiGUUco4kngUTGMJZxjGcCE5nEZKYwlWlUHVX1eAYzmcVs5lTi9ipWs4a1JFXg+2a2sJVtbK8kAUc4yjHJbUb5LPwFOavBzA==

HVSDRfVqSETalGbOvhSl3rUx48G+BNAQxrRWFwPpAlNJQvNCKa5OBmCh1Ba4CWMlrSiNW1oSzva04GOdKIzXehKN7qLBz0lO+FE0JtI+tCXfkQRTX8GMJBBDGYIQxnGcEYQw0hiGUUco4kngUTGMJZxjGcCE5nEZKYwlWlUHVX1eAYzmcVs5lTi9ipWs4a1JFXg+2a2sJVtbK8kAUc4yjHJbUb5LPwFOavBzA==

12 ms

e

e

14 ms

collect

collect

78 ms

fbds.js

fbds.js

208 ms

cbar.js.php

cbar.js.php

29 ms

hotjar-57375.js

hotjar-57375.js

201 ms

settings.js

settings.js

30 ms

ajax-loader.gif

ajax-loader.gif

40 ms

media.nl

media.nl

25 ms

data.js.php

data.js.php

235 ms

p.gif

p.gif

200 ms

b.min.js

b.min.js

8 ms

delivery.js

delivery.js

79 ms

bcm.js

bcm.js

152 ms

ga-audiences

ga-audiences

151 ms

jquery.min.js

jquery.min.js

141 ms

update.html

update.html

1066 ms

event

event

57 ms

event

event

60 ms

s

s

53 ms

event

event

45 ms

event

event

48 ms

event

event

47 ms

config.js

config.js

168 ms

modules-1f5c71aea63f8df71401422ed80fbe5f.js

modules-1f5c71aea63f8df71401422ed80fbe5f.js

32 ms

99 ms

visit-data

visit-data

206 ms

config

config

105 ms

data.js.php

data.js.php

88 ms

widget_v2.132.js

widget_v2.132.js

21 ms

logo.png

logo.png

5 ms

media.nl

media.nl

4 ms

main-banner-icon1.jpg

main-banner-icon1.jpg

6 ms

main-banner-icon2.png

main-banner-icon2.png

5 ms

main-banner-icon3.png

main-banner-icon3.png

6 ms

polyfills.js

polyfills.js

35 ms

31 ms

data.js.php

data.js.php

90 ms

config.js

config.js

26 ms

JWJNEOOQIREYNO2ULCEVXL.js

JWJNEOOQIREYNO2ULCEVXL.js

242 ms

IMG_9965.jpg

IMG_9965.jpg

45 ms

popup.js

popup.js

26 ms

close_square_new.png

close_square_new.png

50 ms

Awesome-Stamp-Logo.jpg

Awesome-Stamp-Logo.jpg

82 ms

Accessibility Review

awesomemerchandise.com accessibility score

72

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

awesomemerchandise.com best practices score

67

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

awesomemerchandise.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

awesomemerchandise.com

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