Tools & Wizards About Us
awesomemerchandise.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

awesomemerchandise.com

Print.inc - Awesome Merchandise

Page Load Speed

3.7 sec in total

First Response

16 ms

Resources Loaded

3.2 sec

Page Rendered

502 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

Visit awesomemerchandise.com

Key Findings

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

Performance Metrics

awesomemerchandise.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,320 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.746

6/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

awesomemerchandise.com

16 ms

awesome-merchandise

1015 ms

gtm.js

57 ms

generalgroup.min.js

346 ms

banner.js

284 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Awesomemerchandise.com, 77% (47 requests) were made to Print.inc and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Print.inc.

Page Optimization Overview & Recommendations

Page size can be reduced by 455.2 kB (11%)

Content Size

4.1 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Awesomemerchandise.com main page is 4.1 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. Only a small number of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 74.1 kB

  • Original 88.9 kB
  • After minification 76.0 kB
  • After compression 14.8 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 12.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 74.1 kB or 83% of the original size.

Image Optimization

-9%

Potential reduce by 269.2 kB

  • Original 3.1 MB
  • After minification 2.8 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. Awesome Merchandise images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 109.9 kB

  • Original 761.7 kB
  • After minification 757.2 kB
  • After compression 651.8 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 109.9 kB or 14% of the original size.

CSS Optimization

-1%

Potential reduce by 2.0 kB

  • Original 180.9 kB
  • After minification 180.9 kB
  • After compression 178.8 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (69%)

Requests Now

39

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 39 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 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

awesomemerchandise.com

awesomemerchandise.com

16 ms

awesome-merchandise

awesome-merchandise

1015 ms

gtm.js

gtm.js

57 ms

generalgroup.min.js

generalgroup.min.js

346 ms

banner.js

banner.js

284 ms

modernizr-2.5.3-respond-1.1.0.min.js

modernizr-2.5.3-respond-1.1.0.min.js

286 ms

awesomplete.js

awesomplete.js

287 ms

all.min.css

all.min.css

415 ms

v4-shims.min.css

v4-shims.min.css

283 ms

CSS

CSS

659 ms

owl.carousel.min.css

owl.carousel.min.css

426 ms

owl.theme.default.min.css

owl.theme.default.min.css

426 ms

26283200.js

26283200.js

527 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

26 ms

1

1

425 ms

Bundle

Bundle

539 ms

classic-071822.css

classic-071822.css

26 ms

mc-validate.js

mc-validate.js

203 ms

owl.carousel.min.js

owl.carousel.min.js

458 ms

scripts.js

scripts.js

452 ms

manifest.js

manifest.js

420 ms

vendor.js

vendor.js

731 ms

frontend.js

frontend.js

821 ms

js

js

43 ms

js

js

79 ms

conversations-embed.js

conversations-embed.js

446 ms

26283200.js

26283200.js

553 ms

fb.js

fb.js

521 ms

banner.js

banner.js

571 ms

collectedforms.js

collectedforms.js

571 ms

fbevents.js

fbevents.js

23 ms

printinc-logo.svg

printinc-logo.svg

98 ms

GetFile

GetFile

1017 ms

GetFile

GetFile

602 ms

GetFile

GetFile

689 ms

GetFile

GetFile

596 ms

GetFile

GetFile

674 ms

GetFile

GetFile

594 ms

GetFile

GetFile

810 ms

GetFile

GetFile

809 ms

Futura%20Bold%20font.ttf

Futura%20Bold%20font.ttf

785 ms

Montserrat-cf-normal-400.ttf

Montserrat-cf-normal-400.ttf

741 ms

Montserrat-cf-normal-500.ttf

Montserrat-cf-normal-500.ttf

762 ms

Montserrat-cf-normal-300.ttf

Montserrat-cf-normal-300.ttf

904 ms

Montserrat-cf-normal-200.ttf

Montserrat-cf-normal-200.ttf

967 ms

Montserrat-cf-normal-100.ttf

Montserrat-cf-normal-100.ttf

904 ms

Montserrat-cf-normal-600.ttf

Montserrat-cf-normal-600.ttf

874 ms

Montserrat-cf-normal-700.ttf

Montserrat-cf-normal-700.ttf

883 ms

Montserrat-cf-normal-800.ttf

Montserrat-cf-normal-800.ttf

996 ms

Montserrat-cf-normal-900.ttf

Montserrat-cf-normal-900.ttf

995 ms

Roboto-cf-normal-400.ttf

Roboto-cf-normal-400.ttf

998 ms

Roboto-cf-normal-500.ttf

Roboto-cf-normal-500.ttf

997 ms

Roboto-cf-normal-300.ttf

Roboto-cf-normal-300.ttf

1063 ms

Roboto-cf-normal-100.ttf

Roboto-cf-normal-100.ttf

1140 ms

Roboto-cf-normal-700.ttf

Roboto-cf-normal-700.ttf

1122 ms

Roboto-cf-normal-900.ttf

Roboto-cf-normal-900.ttf

1123 ms

fa-solid-900.woff

fa-solid-900.woff

1058 ms

fa-regular-400.woff

fa-regular-400.woff

1142 ms

fa-light-300.woff

fa-light-300.woff

1132 ms

GetFile

GetFile

1232 ms

fa-brands-400.woff

fa-brands-400.woff

992 ms

Accessibility Review

awesomemerchandise.com accessibility score

82

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

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

awesomemerchandise.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

awesomemerchandise.com SEO score

84

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 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: