Tools & Wizards About Us
sand.ee screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

sand.ee

Sandee - The Top List of Beaches All Over the World

Page Load Speed

4.1 sec in total

First Response

63 ms

Resources Loaded

3.6 sec

Page Rendered

522 ms

sand.ee screenshot

About Website

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

Sandee is the most comprehensive list of beaches around the world! Sandee includes over 100,000 beaches in every country of the world. Includes activities, photos, maps, and reviews.

Visit sand.ee

Key Findings

We analyzed Sand.ee page load time and found that the first response time was 63 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

sand.ee performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value630 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

sandee.com

63 ms

dd6ba4cea97c4c42.css

14 ms

ca71705f490c83c8.css

20 ms

fd9d1056-d1a7921b4d790826.js

27 ms

4938-03cfe28d6017721d.js

21 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sand.ee, 1% (1 request) were made to . The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Sandee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 578.5 kB (7%)

Content Size

8.3 MB

After Optimization

7.7 MB

  • HTML
  • Images

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

HTML Optimization

-90%

Potential reduce by 574.9 kB

  • Original 637.0 kB
  • After minification 635.9 kB
  • After compression 62.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 574.9 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 3.6 kB

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

Requests Breakdown

Number of requests can be reduced by 25 (33%)

Requests Now

76

After Optimization

51

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sandee.com

sandee.com

63 ms

dd6ba4cea97c4c42.css

dd6ba4cea97c4c42.css

14 ms

ca71705f490c83c8.css

ca71705f490c83c8.css

20 ms

fd9d1056-d1a7921b4d790826.js

fd9d1056-d1a7921b4d790826.js

27 ms

4938-03cfe28d6017721d.js

4938-03cfe28d6017721d.js

21 ms

main-app-2f3800c6e4826db2.js

main-app-2f3800c6e4826db2.js

20 ms

27f96df6-8a204c1130faa2b5.js

27f96df6-8a204c1130faa2b5.js

21 ms

4569-b96c0a6cbbac3666.js

4569-b96c0a6cbbac3666.js

18 ms

1749-060df907cb07ab6e.js

1749-060df907cb07ab6e.js

22 ms

7799-8c9a00502c2cd443.js

7799-8c9a00502c2cd443.js

31 ms

4275-a1de9288d8dddcca.js

4275-a1de9288d8dddcca.js

32 ms

9082-6b5e64afb036054a.js

9082-6b5e64afb036054a.js

23 ms

7325-c4254c5617f53617.js

7325-c4254c5617f53617.js

31 ms

6748-8799e6c7657f0faf.js

6748-8799e6c7657f0faf.js

31 ms

2848-0727c985a857df32.js

2848-0727c985a857df32.js

31 ms

6973-a36f37b1a36e4a26.js

6973-a36f37b1a36e4a26.js

32 ms

7609-29201157dbd72834.js

7609-29201157dbd72834.js

32 ms

2751-fb3da590bf93008e.js

2751-fb3da590bf93008e.js

31 ms

layout-04c44601a60b7e0a.js

layout-04c44601a60b7e0a.js

32 ms

8530-9cdec307eed41a4e.js

8530-9cdec307eed41a4e.js

35 ms

layout-6d0e4b070da14205.js

layout-6d0e4b070da14205.js

35 ms

error-094788ed60651988.js

error-094788ed60651988.js

36 ms

8054-22e96165e2a39e23.js

8054-22e96165e2a39e23.js

36 ms

2173-9cc4b27d028b7773.js

2173-9cc4b27d028b7773.js

35 ms

9791-82323093f3f98276.js

9791-82323093f3f98276.js

35 ms

7340-b247dda7cf679932.js

7340-b247dda7cf679932.js

38 ms

page-559c47f5c28d0f7a.js

page-559c47f5c28d0f7a.js

36 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

37 ms

webpack-4d0441391f326850.js

webpack-4d0441391f326850.js

31 ms

image

image

11 ms

image

image

8 ms

image

image

111 ms

image

image

12 ms

image

image

80 ms

image

image

32 ms

image

image

16 ms

image

image

54 ms

image

image

483 ms

image

image

22 ms

image

image

37 ms

image

image

63 ms

image

image

53 ms

image

image

128 ms

image

image

329 ms

image

image

301 ms

image

image

86 ms

image

image

92 ms

image

image

438 ms

image

image

409 ms

nextlist.svg

nextlist.svg

130 ms

image

image

135 ms

image

image

425 ms

image

image

338 ms

image

image

374 ms

image

image

378 ms

image

image

428 ms

image

image

411 ms

image

image

458 ms

image

image

447 ms

image

image

440 ms

image

image

479 ms

image

image

726 ms

image

image

448 ms

image

image

3210 ms

Manrope-Regular.ttf

Manrope-Regular.ttf

480 ms

Manrope-Medium.ttf

Manrope-Medium.ttf

462 ms

Manrope-Light.ttf

Manrope-Light.ttf

472 ms

Manrope-ExtraLight.ttf

Manrope-ExtraLight.ttf

501 ms

Manrope-SemiBold.ttf

Manrope-SemiBold.ttf

496 ms

Manrope-Bold.ttf

Manrope-Bold.ttf

488 ms

Manrope-ExtraBold.ttf

Manrope-ExtraBold.ttf

478 ms

image

image

473 ms

image

image

848 ms

image

image

803 ms

image

image

448 ms

image

image

475 ms

image

image

453 ms

image

image

715 ms

image

image

500 ms

image

image

486 ms

image

image

623 ms

image

image

765 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

0 ms

image

image

545 ms

image

image

483 ms

Accessibility Review

sand.ee accessibility score

96

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.

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

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

High

Serves images with low resolution

SEO Factors

sand.ee SEO score

100

Search Engine Optimization Advices

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

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 Sand.ee 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 Sand.ee 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

sand.ee

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