Tools & Wizards About Us
andwander.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

andwander.com

and wander ONLINE STORE

Page Load Speed

3.4 sec in total

First Response

686 ms

Resources Loaded

2.5 sec

Page Rendered

198 ms

andwander.com screenshot

About Website

Visit andwander.com now to see the best up-to-date And Wander content for Japan and also check out these interesting facts you probably never knew about andwander.com

東京を拠点に置くアウトドアブランド and wander（アンドワンダー）のオンラインショップです。

Visit andwander.com

Key Findings

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

Performance Metrics

andwander.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

andwander.com

686 ms

reset.css

175 ms

swiper.css

318 ms

general.css

316 ms

widgets.js

6 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 79% of them (22 requests) were addressed to the original Andwander.com, 7% (2 requests) were made to Apis.google.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Andwander.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.8 kB (37%)

Content Size

535.4 kB

After Optimization

339.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Andwander.com main page is 535.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 299.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.9 kB

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 3.4 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 12.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 398 B

  • Original 189.2 kB
  • After minification 188.8 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. And Wander images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 157.1 kB

  • Original 299.2 kB
  • After minification 293.1 kB
  • After compression 142.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 157.1 kB or 53% of the original size.

CSS Optimization

-83%

Potential reduce by 25.5 kB

  • Original 30.8 kB
  • After minification 24.5 kB
  • After compression 5.3 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. Andwander.com needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (70%)

Requests Now

27

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

andwander.com

andwander.com

686 ms

reset.css

reset.css

175 ms

swiper.css

swiper.css

318 ms

general.css

general.css

316 ms

widgets.js

widgets.js

6 ms

plusone.js

plusone.js

85 ms

js

js

57 ms

jquery.min.js

jquery.min.js

518 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

333 ms

jquery.easing.js

jquery.easing.js

348 ms

swiper.jquery.min.js

swiper.jquery.min.js

538 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

470 ms

common.js

common.js

473 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

header_id.png

header_id.png

174 ms

btn_menu.png

btn_menu.png

183 ms

loading.gif

loading.gif

162 ms

btn_left.png

btn_left.png

159 ms

btn_right.png

btn_right.png

167 ms

analytics.js

analytics.js

51 ms

footer.html

footer.html

287 ms

topNav.html

topNav.html

445 ms

img_001.jpg

img_001.jpg

1029 ms

collect

collect

13 ms

social_facebook.png

social_facebook.png

174 ms

social_twitter.png

social_twitter.png

178 ms

social_instagram.png

social_instagram.png

156 ms

sp.css

sp.css

172 ms

Accessibility Review

andwander.com accessibility score

65

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

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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 IDs are not unique

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

andwander.com SEO score

75

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Andwander.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Andwander.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

andwander.com

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