Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

vanilla-sand.com

Sustainable Swimwear & Eco-Friendly Beachwear | Vanilla Sand

Page Load Speed

5.3 sec in total

First Response

489 ms

Resources Loaded

4.1 sec

Page Rendered

713 ms

About Website

Visit vanilla-sand.com now to see the best up-to-date Vanilla Sand content and also check out these interesting facts you probably never knew about vanilla-sand.com

Shop our sustainable swimwear and eco-friendly beachwear made from recycled ocean plastic and 100% organic materials. Ethically made in Portugal and Brazil.

Visit vanilla-sand.com

Key Findings

We analyzed Vanilla-sand.com page load time and found that the first response time was 489 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

vanilla-sand.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

vanilla-sand.com

489 ms

vanilla-sand.com

477 ms

sbi-styles.min.css

461 ms

style.min.css

69 ms

mediaelementplayer-legacy.min.css

74 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 90% of them (114 requests) were addressed to the original Vanilla-sand.com, 2% (2 requests) were made to Stats.wp.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Vanilla-sand.com.

Page Optimization Overview & Recommendations

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

Content Size

6.0 MB

After Optimization

5.7 MB

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

HTML Optimization

-85%

Potential reduce by 176.0 kB

  • Original 208.2 kB
  • After minification 192.7 kB
  • After compression 32.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 176.0 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 101.5 kB

  • Original 5.4 MB
  • After minification 5.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. Vanilla Sand images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.6 kB

  • Original 294.1 kB
  • After minification 294.1 kB
  • After compression 288.4 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

-2%

Potential reduce by 2.5 kB

  • Original 104.6 kB
  • After minification 104.4 kB
  • After compression 102.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. Vanilla-sand.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (54%)

Requests Now

122

After Optimization

56

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

Accessibility Review

vanilla-sand.com accessibility score

71

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

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.

Best Practices

vanilla-sand.com best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

vanilla-sand.com SEO score

83

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 Vanilla-sand.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 Vanilla-sand.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

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