Tools & Wizards About Us
happythings.eu screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

happythings.eu

HappyThings - HappyThings

Page Load Speed

5.9 sec in total

First Response

434 ms

Resources Loaded

5.4 sec

Page Rendered

99 ms

happythings.eu screenshot

About Website

Click here to check amazing Happy Things content for Netherlands. Otherwise, check out these important facts you probably never knew about happythings.eu

HappyThings THE webshop with polymer clay, beads and more

Visit happythings.eu

Key Findings

We analyzed Happythings.eu page load time and found that the first response time was 434 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

happythings.eu performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.294

41/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

happythings.eu

434 ms

jquery-ui-1.8.7.custom.css

338 ms

jquery-1.4.4.min.js

569 ms

jqueryadd2cart.js

330 ms

jquery-ui-1.8.7.custom.min.js

821 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 72% of them (31 requests) were addressed to the original Happythings.eu, 9% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Happythings.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (87%)

Content Size

1.8 MB

After Optimization

232.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Happythings.eu main page is 1.8 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. 25% of websites need less resources to load. HTML takes 970.6 kB which makes up the majority of the site volume.

HTML Optimization

-99%

Potential reduce by 961.0 kB

  • Original 970.6 kB
  • After minification 49.4 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 921.1 kB, which is 95% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 961.0 kB or 99% of the original size.

Image Optimization

-66%

Potential reduce by 144.0 kB

  • Original 218.4 kB
  • After minification 74.4 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. Obviously, Happy Things needs image optimization as it can save up to 144.0 kB or 66% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 319.3 kB

  • Original 438.4 kB
  • After minification 401.6 kB
  • After compression 119.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 319.3 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 153.8 kB

  • Original 183.0 kB
  • After minification 158.9 kB
  • After compression 29.2 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. Happythings.eu needs all CSS files to be minified and compressed as it can save up to 153.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (58%)

Requests Now

38

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

happythings.eu

happythings.eu

434 ms

jquery-ui-1.8.7.custom.css

jquery-ui-1.8.7.custom.css

338 ms

jquery-1.4.4.min.js

jquery-1.4.4.min.js

569 ms

jqueryadd2cart.js

jqueryadd2cart.js

330 ms

jquery-ui-1.8.7.custom.min.js

jquery-ui-1.8.7.custom.min.js

821 ms

css

css

63 ms

_cataloge.css

_cataloge.css

664 ms

no_bars.css

no_bars.css

378 ms

firefox-styles.css

firefox-styles.css

805 ms

SpryAccordion.js

SpryAccordion.js

812 ms

cloud-zoom.1.0.2.min.js

cloud-zoom.1.0.2.min.js

981 ms

cloud-zoom.css

cloud-zoom.css

1180 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

1437 ms

custom_form_elements.js

custom_form_elements.js

1685 ms

jquery.min.js

jquery.min.js

39 ms

jquery.ui.core.js

jquery.ui.core.js

1704 ms

jquery.ui.widget.js

jquery.ui.widget.js

1705 ms

jquery.ui.position.js

jquery.ui.position.js

1960 ms

jquery.ui.autocomplete.js

jquery.ui.autocomplete.js

1968 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

2505 ms

prettyPhoto.css

prettyPhoto.css

2508 ms

0_customized.css

0_customized.css

2521 ms

fb_nl.js

fb_nl.js

2523 ms

analytics.js

analytics.js

18 ms

collect

collect

25 ms

3__18__ms1.rvf_1.jpg

3__18__ms1.rvf_1.jpg

1759 ms

cb_17.jpg

cb_17.jpg

814 ms

all.js

all.js

161 ms

nl_search.xml

nl_search.xml

1285 ms

topbasket.png

topbasket.png

830 ms

search.png

search.png

831 ms

b_normal.png

b_normal.png

1631 ms

bg_tmenu_ull.png

bg_tmenu_ull.png

1972 ms

arrow_8.png

arrow_8.png

2373 ms

arrow-6.png

arrow-6.png

1629 ms

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

51 ms

PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf

PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf

59 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

70 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

100 ms

162 ms

xd_arbiter.php

xd_arbiter.php

120 ms

xd_arbiter.php

xd_arbiter.php

235 ms

index.php

index.php

965 ms

Accessibility Review

happythings.eu accessibility score

71

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

Form elements do not have associated labels

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

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 valid value for its [lang] attribute.

High

[lang] attributes do not have a valid value

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

happythings.eu best practices score

83

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

Page has valid source maps

SEO Factors

happythings.eu SEO score

97

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

High

Tap targets are not sized appropriately

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 Happythings.eu 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 Happythings.eu 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

happythings.eu

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