Tools & Wizards About Us
waveinn.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

waveinn.com

Waveinn | Online store for nautical and fishing equipment

Page Load Speed

3.4 sec in total

First Response

157 ms

Resources Loaded

1.6 sec

Page Rendered

1.6 sec

waveinn.com screenshot

About Website

Click here to check amazing Waveinn content for Japan. Otherwise, check out these important facts you probably never knew about waveinn.com

Online store of fishing and nautical equipment. Find in Waveinn fishing rods, fishing equipment, reels and lures | Best price.

Visit waveinn.com

Key Findings

We analyzed Waveinn.com page load time and found that the first response time was 157 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 60% of websites can load faster.

Performance Metrics

waveinn.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value2,370 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.166

71/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

waveinn.com

157 ms

waveinn

589 ms

gtm.js

107 ms

t.js

24 ms

otSDKStub.js

33 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Waveinn.com, 69% (76 requests) were made to Cache.tradeinn.com and 10% (11 requests) were made to Tradeinn.com. The less responsive or slowest element that took the longest time to load (760 ms) relates to the external source Cache.tradeinn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.7 kB (15%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waveinn.com main page is 1.3 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. 65% of websites need less resources to load. Images take 780.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 177.6 kB

  • Original 212.7 kB
  • After minification 192.3 kB
  • After compression 35.1 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 177.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 780.8 kB
  • After minification 778.2 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. Waveinn images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 225.3 kB
  • After minification 225.3 kB
  • After compression 223.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 884 B

  • Original 33.4 kB
  • After minification 33.4 kB
  • After compression 32.5 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. Waveinn.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

100

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

waveinn.com

waveinn.com

157 ms

waveinn

waveinn

589 ms

gtm.js

gtm.js

107 ms

t.js

t.js

24 ms

otSDKStub.js

otSDKStub.js

33 ms

header.css

header.css

33 ms

home.css

home.css

182 ms

e532a544-2e9c-4473-8a87-3e1f4afb0942.json

e532a544-2e9c-4473-8a87-3e1f4afb0942.json

30 ms

css2

css2

66 ms

flechaxxs_down_gris.svg

flechaxxs_down_gris.svg

210 ms

flechabannerhp_izq_blanca.svg

flechabannerhp_izq_blanca.svg

183 ms

waveinn.svg

waveinn.svg

205 ms

diveinnmini.svg

diveinnmini.svg

215 ms

waveinnmini.svg

waveinnmini.svg

214 ms

swiminnmini.svg

swiminnmini.svg

218 ms

snowinnmini.svg

snowinnmini.svg

216 ms

trekkinnmini.svg

trekkinnmini.svg

218 ms

runnerinnmini.svg

runnerinnmini.svg

212 ms

bikeinnmini.svg

bikeinnmini.svg

225 ms

traininnmini.svg

traininnmini.svg

230 ms

smashinnmini.svg

smashinnmini.svg

228 ms

goalinnmini.svg

goalinnmini.svg

230 ms

xtremeinnmmini.svg

xtremeinnmmini.svg

234 ms

motardinnmini.svg

motardinnmini.svg

227 ms

dressinnmini.svg

dressinnmini.svg

246 ms

kidinnmini.svg

kidinnmini.svg

256 ms

techinnmini.svg

techinnmini.svg

244 ms

bricoinnmini.svg

bricoinnmini.svg

241 ms

outletinnmini.svg

outletinnmini.svg

258 ms

sports_b.svg

sports_b.svg

245 ms

micuenta.svg

micuenta.svg

256 ms

carrito.svg

carrito.svg

256 ms

techinn-thmini.jpg

techinn-thmini.jpg

258 ms

bricoinn-thmini.jpg

bricoinn-thmini.jpg

255 ms

outletinn-thmini.jpg

outletinn-thmini.jpg

260 ms

+sports.svg

+sports.svg

260 ms

HP-raymarine-jun24.jpg

HP-raymarine-jun24.jpg

373 ms

raymarine_l.png

raymarine_l.png

370 ms

typhoone_wave.jpg

typhoone_wave.jpg

757 ms

typhoone_b_l.png

typhoone_b_l.png

349 ms

HP-molix-oct23.jpg

HP-molix-oct23.jpg

760 ms

molix_b_l.png

molix_b_l.png

352 ms

3704.jpg

3704.jpg

353 ms

387.jpg

387.jpg

368 ms

78.jpg

78.jpg

367 ms

1551.jpg

1551.jpg

369 ms

flechabannerhp_der_blanca.svg

flechabannerhp_der_blanca.svg

588 ms

flechabannerhp_izq_gris.svg

flechabannerhp_izq_gris.svg

223 ms

flechabannerhp_der_gris.svg

flechabannerhp_der_gris.svg

219 ms

otBannerSdk.js

otBannerSdk.js

85 ms

listado.min.js

listado.min.js

6 ms

home.min.js

home.min.js

161 ms

footer.css

footer.css

5 ms

fancybox.umd.js

fancybox.umd.js

11 ms

fancybox.min.css

fancybox.min.css

339 ms

header.min.js

header.min.js

373 ms

base.min.js

base.min.js

101 ms

en.json

en.json

111 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

93 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

101 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

106 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

111 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

114 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

110 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

109 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

109 ms

90.jpg

90.jpg

175 ms

448.jpg

448.jpg

281 ms

446.jpg

446.jpg

165 ms

1529.jpg

1529.jpg

164 ms

401.jpg

401.jpg

163 ms

960.jpg

960.jpg

164 ms

1285.jpg

1285.jpg

164 ms

329.jpg

329.jpg

165 ms

1547.jpg

1547.jpg

158 ms

7007-grande.jpg

7007-grande.jpg

327 ms

11272-grande.jpg

11272-grande.jpg

257 ms

7009-peke.jpg

7009-peke.jpg

245 ms

11048-peke.jpg

11048-peke.jpg

343 ms

7016-peke.jpg

7016-peke.jpg

404 ms

whatsApp.svg

whatsApp.svg

244 ms

chat_icono.svg

chat_icono.svg

250 ms

applesotre.svg

applesotre.svg

252 ms

otFlat.json

otFlat.json

20 ms

otPcPanel.json

otPcPanel.json

40 ms

otCommonStyles.css

otCommonStyles.css

39 ms

googleplay.svg

googleplay.svg

250 ms

flechamini_down_gris.svg

flechamini_down_gris.svg

247 ms

spa_opinionesverificadas.png

spa_opinionesverificadas.png

248 ms

co2neutre.svg

co2neutre.svg

253 ms

tgcbinn_gris.svg

tgcbinn_gris.svg

264 ms

fb.svg

fb.svg

265 ms

ig.svg

ig.svg

266 ms

yt.svg

yt.svg

265 ms

lab_footer.svg

lab_footer.svg

264 ms

powered_by_logo.svg

powered_by_logo.svg

14 ms

paypal_gris.svg

paypal_gris.svg

178 ms

visa_gris.svg

visa_gris.svg

176 ms

mastercard_gris.svg

mastercard_gris.svg

176 ms

applepay_gris.svg

applepay_gris.svg

163 ms

americalexpress_gris.svg

americalexpress_gris.svg

163 ms

adyen_gris.svg

adyen_gris.svg

164 ms

verisign_gris.svg

verisign_gris.svg

167 ms

netrivals_gris.svg

netrivals_gris.svg

168 ms

confianzaonlineeurop_gris.svg

confianzaonlineeurop_gris.svg

169 ms

geotrust_gris.svg

geotrust_gris.svg

171 ms

securutypayment_gris.svg

securutypayment_gris.svg

173 ms

scalapay_gris.svg

scalapay_gris.svg

175 ms

klarna_gris.svg

klarna_gris.svg

176 ms

tradeinn_negre.svg

tradeinn_negre.svg

176 ms

Accessibility Review

waveinn.com accessibility score

86

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

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

waveinn.com SEO score

77

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

Document doesn't have a valid hreflang

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

waveinn.com

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