Tools & Wizards About Us
storkplay.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

storkplay.com

Interactive Sandbox / Floor | Buy Augmented Reality Sandbox

Page Load Speed

4.8 sec in total

First Response

703 ms

Resources Loaded

3.3 sec

Page Rendered

815 ms

storkplay.com screenshot

About Website

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

Augmented reality sandbox / floor / table. Interactive educational and entertaining world for children. AR sandbox solution for sand therapy, snoezelen development at home / school / kindergarten.

Visit storkplay.com

Key Findings

We analyzed Storkplay.com page load time and found that the first response time was 703 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

storkplay.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

storkplay.com

703 ms

page_9c69e4eee740f52e1b93637b271e0eb8_v1.css

279 ms

style_r.css

289 ms

style.css

285 ms

scroll.css

283 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 83% of them (59 requests) were addressed to the original Storkplay.com, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Storkplay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.3 kB (4%)

Content Size

3.4 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Storkplay.com main page is 3.4 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 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 35.1 kB

  • Original 46.6 kB
  • After minification 44.5 kB
  • After compression 11.6 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 35.1 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 78.1 kB

  • Original 3.0 MB
  • After minification 2.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. Storkplay images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.2 kB

  • Original 334.6 kB
  • After minification 334.6 kB
  • After compression 327.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

-19%

Potential reduce by 3.9 kB

  • Original 20.4 kB
  • After minification 20.4 kB
  • After compression 16.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. Storkplay.com needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (48%)

Requests Now

66

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

storkplay.com

storkplay.com

703 ms

page_9c69e4eee740f52e1b93637b271e0eb8_v1.css

page_9c69e4eee740f52e1b93637b271e0eb8_v1.css

279 ms

style_r.css

style_r.css

289 ms

style.css

style.css

285 ms

scroll.css

scroll.css

283 ms

burger.css

burger.css

284 ms

popup.css

popup.css

287 ms

css

css

43 ms

css

css

55 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

428 ms

hammer.min.js

hammer.min.js

426 ms

jquery.vide.min.js

jquery.vide.min.js

425 ms

scroll.js

scroll.js

426 ms

prlx.js

prlx.js

426 ms

three.min.js

three.min.js

880 ms

OBJLoader.js

OBJLoader.js

566 ms

MTLLoader.js

MTLLoader.js

567 ms

EffectComposer.js

EffectComposer.js

566 ms

LuminosityHighPassShader.js

LuminosityHighPassShader.js

567 ms

RenderPass.js

RenderPass.js

568 ms

ShaderPass.js

ShaderPass.js

707 ms

CopyShader.js

CopyShader.js

708 ms

UnrealBloomPass.js

UnrealBloomPass.js

708 ms

3d.js

3d.js

709 ms

popup.js

popup.js

710 ms

js

js

73 ms

header.js

header.js

847 ms

custom.js

custom.js

848 ms

owl.carousel.min.css

owl.carousel.min.css

719 ms

owl.theme.default.min.css

owl.theme.default.min.css

720 ms

owl.carousel.min.js

owl.carousel.min.js

723 ms

ba.js

ba.js

175 ms

logo-bricks.svg

logo-bricks.svg

231 ms

sandbox-vs-min.png

sandbox-vs-min.png

500 ms

npic1.png

npic1.png

568 ms

npic2.png

npic2.png

566 ms

npic3.png

npic3.png

621 ms

npic4.png

npic4.png

568 ms

tag.js

tag.js

894 ms

stork.jpg

stork.jpg

468 ms

star.svg

star.svg

599 ms

trex.png

trex.png

754 ms

stars.png

stars.png

666 ms

earth.png

earth.png

818 ms

satellite.png

satellite.png

819 ms

entertainment-bg.svg

entertainment-bg.svg

718 ms

sp-products.png

sp-products.png

744 ms

form_block_bg.svg

form_block_bg.svg

807 ms

1d63426a12f0998735ff22673354073d.jpg

1d63426a12f0998735ff22673354073d.jpg

1004 ms

83bf139a388db6d9acca6530cd194a0c.png

83bf139a388db6d9acca6530cd194a0c.png

967 ms

ed6fadb5a88bc8b08ab42585ba75ec6d.jpg

ed6fadb5a88bc8b08ab42585ba75ec6d.jpg

967 ms

309e68b8c848cbe94963eede992e63f9.jpg

309e68b8c848cbe94963eede992e63f9.jpg

968 ms

17fe3641c138b4e16d2cb451a9a6950d.jpeg

17fe3641c138b4e16d2cb451a9a6950d.jpeg

969 ms

bbfb4a79ea2bb23e0aafe879e8aa8719.jpeg

bbfb4a79ea2bb23e0aafe879e8aa8719.jpeg

970 ms

744d334d5c4db074ddcd9fa9b5886278.jpg

744d334d5c4db074ddcd9fa9b5886278.jpg

1036 ms

bc5cba4cb8a81e749fe467189d91f294.png

bc5cba4cb8a81e749fe467189d91f294.png

1184 ms

0766b792c6ddf26a5ea7c680878b7180.png

0766b792c6ddf26a5ea7c680878b7180.png

1101 ms

52838e0695f5a150d49e6d4284db987a.jpg

52838e0695f5a150d49e6d4284db987a.jpg

1112 ms

js

js

49 ms

analytics.js

analytics.js

44 ms

bx_stat

bx_stat

122 ms

proxima_nova_regular-webfont.woff

proxima_nova_regular-webfont.woff

1045 ms

proxima_nova_semibold-webfont.woff

proxima_nova_semibold-webfont.woff

1084 ms

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0C46sNz-4.ttf

VdGBAYIAV6gnpUpoWwNkYvrugw9RuM0C46sNz-4.ttf

183 ms

collect

collect

26 ms

stork-new.gif

stork-new.gif

1079 ms

stork-new.jpg

stork-new.jpg

1145 ms

stork-new.jpeg

stork-new.jpeg

1158 ms

stork-new.png

stork-new.png

1175 ms

advert.gif

advert.gif

673 ms

sync_cookie_image_decide

sync_cookie_image_decide

147 ms

Accessibility Review

storkplay.com accessibility score

62

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

storkplay.com best practices score

67

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

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

storkplay.com SEO score

85

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 uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storkplay.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Storkplay.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

storkplay.com

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