Tools & Wizards About Us
share.homage.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

share.homage.com

Vintage Apparel | Retro & Vintage Clothing | HOMAGE

Page Load Speed

11.8 sec in total

First Response

134 ms

Resources Loaded

4.4 sec

Page Rendered

7.3 sec

share.homage.com screenshot

About Website

Click here to check amazing Share HOMAGE content for United States. Otherwise, check out these important facts you probably never knew about share.homage.com

HOMAGE turns back the clock with shout outs to eclectic moments and personalities in sports, music, politics and political culture with unique vintage apparel.

Visit share.homage.com

Key Findings

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

Performance Metrics

share.homage.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value28.5 s

0/100

10%

TBT (Total Blocking Time)

Value36,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value55.7 s

0/100

10%

Network Requests Diagram

share.homage.com

134 ms

optimize.js

315 ms

all.css

520 ms

css2

405 ms

js

452 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Share.homage.com, 40% (33 requests) were made to Talkable.com and 5% (4 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source 7620365.fs1.hubspotusercontent-na1.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (22%)

Content Size

4.6 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Share.homage.com main page is 4.6 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. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 170.2 kB

  • Original 214.0 kB
  • After minification 207.4 kB
  • After compression 43.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. 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 170.2 kB or 80% of the original size.

Image Optimization

-18%

Potential reduce by 708.7 kB

  • Original 4.0 MB
  • After minification 3.3 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. Obviously, Share HOMAGE needs image optimization as it can save up to 708.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-41%

Potential reduce by 119.6 kB

  • Original 289.4 kB
  • After minification 289.2 kB
  • After compression 169.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 119.6 kB or 41% of the original size.

CSS Optimization

-20%

Potential reduce by 12.6 kB

  • Original 62.4 kB
  • After minification 62.0 kB
  • After compression 49.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. Share.homage.com needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (73%)

Requests Now

77

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

share.homage.com

share.homage.com

134 ms

optimize.js

optimize.js

315 ms

all.css

all.css

520 ms

css2

css2

405 ms

js

js

452 ms

c24478aa372e30ab8365522.js

c24478aa372e30ab8365522.js

288 ms

style.min.css

style.min.css

426 ms

style.css

style.css

408 ms

bundle.css

bundle.css

423 ms

front.min.css

front.min.css

423 ms

jquery.min.js

jquery.min.js

449 ms

jquery-migrate.min.js

jquery-migrate.min.js

411 ms

widget-v2.js

widget-v2.js

403 ms

bundle.js

bundle.js

501 ms

front.min.js

front.min.js

413 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

481 ms

v2.js

v2.js

230 ms

analytics.js

analytics.js

595 ms

gtm.js

gtm.js

501 ms

d97x82mqvq

d97x82mqvq

991 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

813 ms

Depositphotos_442877274_L-min.jpg

Depositphotos_442877274_L-min.jpg

1581 ms

1524147791434.jpeg

1524147791434.jpeg

1739 ms

neutral%20campaign%20screen.png

neutral%20campaign%20screen.png

2533 ms

talkable_logo.svg

talkable_logo.svg

651 ms

hexagon-outline-l.svg

hexagon-outline-l.svg

653 ms

hexagon-outline-s.svg

hexagon-outline-s.svg

650 ms

hexagon-solid-purple.svg

hexagon-solid-purple.svg

620 ms

hexagons-solid-group.svg

hexagons-solid-group.svg

653 ms

hexagon-solid-yellow.svg

hexagon-solid-yellow.svg

662 ms

BHLDN-logo.svg

BHLDN-logo.svg

660 ms

hex_outline_bottom_right.svg

hex_outline_bottom_right.svg

672 ms

hex_outlines_top_left.svg

hex_outlines_top_left.svg

658 ms

hex_red_yellow_group.svg

hex_red_yellow_group.svg

674 ms

hex-solid-orange.svg

hex-solid-orange.svg

678 ms

hex-solid-gold.svg

hex-solid-gold.svg

989 ms

blog-hex-outlines.svg

blog-hex-outlines.svg

1005 ms

hex_outlines_bottom_left.svg

hex_outlines_bottom_left.svg

1002 ms

hex_outline_top_right.svg

hex_outline_top_right.svg

1004 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff

896 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

1373 ms

fa-solid-900.woff

fa-solid-900.woff

801 ms

fa-regular-400.woff

fa-regular-400.woff

874 ms

hex-mask.svg

hex-mask.svg

458 ms

insight.min.js

insight.min.js

836 ms

bat.js

bat.js

834 ms

fbevents.js

fbevents.js

721 ms

conversion_async.js

conversion_async.js

799 ms

7620365.js

7620365.js

319 ms

3844.js

3844.js

783 ms

stat.js

stat.js

782 ms

212509.js

212509.js

796 ms

d97x82mqvq

d97x82mqvq

294 ms

js

js

297 ms

collect

collect

524 ms

clarity.js

clarity.js

474 ms

lftracker_v1_DzLR5a50YvA4BoQ2.js

lftracker_v1_DzLR5a50YvA4BoQ2.js

703 ms

json

json

396 ms

hexagons_solid_image-compressed-1024x874.png

hexagons_solid_image-compressed-1024x874.png

387 ms

1f1fa-1f1e6.svg

1f1fa-1f1e6.svg

356 ms

collect

collect

325 ms

2006935929608551

2006935929608551

342 ms

collectedforms.js

collectedforms.js

830 ms

leadflows.js

leadflows.js

697 ms

fb.js

fb.js

697 ms

7620365.js

7620365.js

694 ms

7620365.js

7620365.js

692 ms

56260067.js

56260067.js

113 ms

shutterfly-logo.png

shutterfly-logo.png

317 ms

toms.png

toms.png

314 ms

puravida.png

puravida.png

318 ms

crate-and-kids-horizontal.png

crate-and-kids-horizontal.png

316 ms

rothys.png

rothys.png

316 ms

tr.lfeeder.com

tr.lfeeder.com

744 ms

json

json

257 ms

56260067

56260067

116 ms

ga-audiences

ga-audiences

707 ms

colourpop-logo.png

colourpop-logo.png

511 ms

27 ms

nr-1216.min.js

nr-1216.min.js

116 ms

4b157f45be

4b157f45be

162 ms

c.gif

c.gif

45 ms

Accessibility Review

share.homage.com accessibility score

84

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

share.homage.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

share.homage.com SEO score

75

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Share.homage.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 Share.homage.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

share.homage.com

Open Graph data is detected on the main page of Share HOMAGE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: