Tools & Wizards About Us
wear2go.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

wear2go.com

Wear2go - Easy Luxury online - Wear2go

Page Load Speed

6.3 sec in total

First Response

339 ms

Resources Loaded

5.5 sec

Page Rendered

384 ms

wear2go.com screenshot

About Website

Welcome to wear2go.com homepage info - get ready to check Wear2go best content for Japan right away, or after learning these important things about wear2go.com

Exclusive online store where you can find all the latest luxury collections at a special price.

Visit wear2go.com

Key Findings

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

Performance Metrics

wear2go.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.226

55/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

wear2go.com

339 ms

www.wear2go.com

422 ms

828 ms

global.css

217 ms

uniform.default.css

321 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 89% of them (99 requests) were addressed to the original Wear2go.com, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (951 ms) belongs to the original domain Wear2go.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.4 kB (5%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wear2go.com main page is 2.2 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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 31.0 kB

  • Original 40.2 kB
  • After minification 36.0 kB
  • After compression 9.2 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 31.0 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 26.9 kB

  • Original 1.9 MB
  • After minification 1.9 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. Wear2go images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 54.0 kB

  • Original 207.2 kB
  • After minification 206.3 kB
  • After compression 153.3 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 54.0 kB or 26% of the original size.

CSS Optimization

-15%

Potential reduce by 10.6 kB

  • Original 69.7 kB
  • After minification 69.4 kB
  • After compression 59.1 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. Wear2go.com needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (71%)

Requests Now

101

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wear2go. 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 38 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wear2go.com

wear2go.com

339 ms

www.wear2go.com

www.wear2go.com

422 ms

828 ms

global.css

global.css

217 ms

uniform.default.css

uniform.default.css

321 ms

jquery.fancybox.css

jquery.fancybox.css

316 ms

product_list.css

product_list.css

318 ms

blockcategories.css

blockcategories.css

322 ms

blockcurrencies.css

blockcurrencies.css

323 ms

blockcontact.css

blockcontact.css

324 ms

blockmyaccount.css

blockmyaccount.css

427 ms

blocknewsletter.css

blocknewsletter.css

424 ms

blocktags.css

blocktags.css

425 ms

blockuserinfo.css

blockuserinfo.css

420 ms

blockpermanentlinks.css

blockpermanentlinks.css

424 ms

blockviewed.css

blockviewed.css

427 ms

tmbrandlogo.css

tmbrandlogo.css

533 ms

blockcart.css

blockcart.css

529 ms

jquery.bxslider.css

jquery.bxslider.css

531 ms

tmfeatureproducts.css

tmfeatureproducts.css

532 ms

tmnewproducts.css

tmnewproducts.css

524 ms

tm_flexslider.css

tm_flexslider.css

533 ms

tmstyle.css

tmstyle.css

632 ms

blocktopmenu.css

blocktopmenu.css

632 ms

superfish-modified.css

superfish-modified.css

638 ms

paypal.css

paypal.css

632 ms

footercustom.css

footercustom.css

636 ms

footercustom-responsive.css

footercustom-responsive.css

639 ms

yetanotheradvancedsearch.css

yetanotheradvancedsearch.css

737 ms

jquery.slider.min.css

jquery.slider.min.css

737 ms

nivo-slider.css

nivo-slider.css

737 ms

blocklanguages.css

blocklanguages.css

740 ms

blocksearch.css

blocksearch.css

738 ms

jquery.autocomplete.css

jquery.autocomplete.css

741 ms

tmstyle.css

tmstyle.css

842 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

951 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

847 ms

jquery.easing.js

jquery.easing.js

845 ms

css

css

34 ms

css

css

50 ms

styles.css

styles.css

838 ms

custom.css

custom.css

620 ms

lightbox.css

lightbox.css

642 ms

animate.css

animate.css

640 ms

tools.js

tools.js

664 ms

global.js

global.js

637 ms

10-bootstrap.min.js

10-bootstrap.min.js

664 ms

15-jquery.total-storage.min.js

15-jquery.total-storage.min.js

742 ms

15-jquery.uniform-modified.js

15-jquery.uniform-modified.js

643 ms

jquery.fancybox.js

jquery.fancybox.js

648 ms

products-comparison.js

products-comparison.js

645 ms

treeManagement.js

treeManagement.js

645 ms

blocknewsletter.js

blocknewsletter.js

650 ms

ajax-cart.js

ajax-cart.js

746 ms

jquery.scrollTo.js

jquery.scrollTo.js

644 ms

jquery.serialScroll.js

jquery.serialScroll.js

643 ms

jquery.bxslider.js

jquery.bxslider.js

643 ms

tm_jquery.flexslider.min.js

tm_jquery.flexslider.min.js

643 ms

hoverIntent.js

hoverIntent.js

640 ms

superfish-modified.js

superfish-modified.js

744 ms

blocktopmenu.js

blocktopmenu.js

648 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

647 ms

yetanotheradvancedsearch.js

yetanotheradvancedsearch.js

650 ms

jquery.slider.min.js

jquery.slider.min.js

649 ms

jquery.cookie.js

jquery.cookie.js

651 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

751 ms

GoogleAnalyticActionLib.js

GoogleAnalyticActionLib.js

651 ms

jquery.autocomplete.js

jquery.autocomplete.js

654 ms

blocksearch.js

blocksearch.js

651 ms

index.js

index.js

645 ms

owl.carousel.js

owl.carousel.js

644 ms

custom.js

custom.js

751 ms

lightbox-2.6.min.js

lightbox-2.6.min.js

646 ms

jquery.elevatezoom.min.js

jquery.elevatezoom.min.js

689 ms

payments.jpg

payments.jpg

502 ms

call.png

call.png

287 ms

logo.jpg

logo.jpg

288 ms

banner2__PE2024_ENG.jpg

banner2__PE2024_ENG.jpg

783 ms

banner3__PE2016.jpg

banner3__PE2016.jpg

808 ms

banner5__AI2015.jpg

banner5__AI2015.jpg

627 ms

98a562f7041dbf190d638e4bb1d220fc.jpg

98a562f7041dbf190d638e4bb1d220fc.jpg

286 ms

efff6d666a4d7d11dcf48d2af88aad40.jpg

efff6d666a4d7d11dcf48d2af88aad40.jpg

314 ms

b706f8d4c23db325e3fd3d86b01fa079.jpg

b706f8d4c23db325e3fd3d86b01fa079.jpg

306 ms

198598b0bff43af9fd269264bc3ca572.jpg

198598b0bff43af9fd269264bc3ca572.jpg

599 ms

footer_img_1.png

footer_img_1.png

388 ms

analytics.js

analytics.js

247 ms

close.png

close.png

440 ms

loading.gif

loading.gif

441 ms

prev.png

prev.png

549 ms

next.png

next.png

548 ms

sprite.png

sprite.png

659 ms

pipe.gif

pipe.gif

657 ms

menu-sepretor.jpg

menu-sepretor.jpg

657 ms

loading.gif

loading.gif

669 ms

social_fb.png

social_fb.png

711 ms

social_twi.png

social_twi.png

712 ms

social_gg.png

social_gg.png

711 ms

social_pin.png

social_pin.png

721 ms

social_blog.png

social_blog.png

771 ms

85513542c28bdf6382d2a27bd.js

85513542c28bdf6382d2a27bd.js

623 ms

back_to_top.png

back_to_top.png

631 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

41 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

853 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5XljLdSL57k.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5XljLdSL57k.ttf

57 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XljLdSL57k.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XljLdSL57k.ttf

58 ms

ec.js

ec.js

13 ms

collect

collect

23 ms

payments.jpg

payments.jpg

539 ms

arrows.png

arrows.png

111 ms

bullets.png

bullets.png

112 ms

Accessibility Review

wear2go.com accessibility score

46

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

wear2go.com best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wear2go.com SEO score

72

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 doesn't use 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 Wear2go.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 Wear2go.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

wear2go.com

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