Tools & Wizards About Us
pureandcure.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

pureandcure.com

The leading Travel Company | Wellbeing, Yoga, Detox, Health and Fitness Holidays Worldwide | Pureandcure

Page Load Speed

3.3 sec in total

First Response

285 ms

Resources Loaded

2.7 sec

Page Rendered

346 ms

pureandcure.com screenshot

About Website

Welcome to pureandcure.com homepage info - get ready to check Pureandcure best content right away, or after learning these important things about pureandcure.com

Let us guide you in finding your perfect Wellbeing Holiday: Safe & Secure ✔ Extra benefits for our Guests ✔ Lowest price guarantee ✔ We know our hotels ✔ Tailor-made Holidays ✔ Official Sales Office

Visit pureandcure.com

Key Findings

We analyzed Pureandcure.com page load time and found that the first response time was 285 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

pureandcure.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.639

9/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

pureandcure.com

285 ms

pureandcure.com

637 ms

css2

26 ms

bootstrap.min.css

170 ms

owl.carousel.min.css

256 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 76% of them (65 requests) were addressed to the original Pureandcure.com, 4% (3 requests) were made to Google.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (786 ms) belongs to the original domain Pureandcure.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.8 kB (27%)

Content Size

761.0 kB

After Optimization

557.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pureandcure.com main page is 761.0 kB. 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. Javascripts take 411.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 185.8 kB

  • Original 217.3 kB
  • After minification 210.2 kB
  • After compression 31.5 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 185.8 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 5.4 kB

  • Original 78.4 kB
  • After minification 73.0 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. Pureandcure images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 12.2 kB

  • Original 411.6 kB
  • After minification 411.6 kB
  • After compression 399.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

-1%

Potential reduce by 427 B

  • Original 53.8 kB
  • After minification 53.8 kB
  • After compression 53.3 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. Pureandcure.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (59%)

Requests Now

79

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pureandcure.com

pureandcure.com

285 ms

pureandcure.com

pureandcure.com

637 ms

css2

css2

26 ms

bootstrap.min.css

bootstrap.min.css

170 ms

owl.carousel.min.css

owl.carousel.min.css

256 ms

owl.theme.default.min.css

owl.theme.default.min.css

264 ms

bootstrap-datepicker3.min.css

bootstrap-datepicker3.min.css

265 ms

datepicker-kv.min.css

datepicker-kv.min.css

273 ms

kv-widgets.min.css

kv-widgets.min.css

273 ms

font-awesome.min.css

font-awesome.min.css

282 ms

site.min.css

site.min.css

342 ms

select2.min.css

select2.min.css

350 ms

select2-addl.min.css

select2-addl.min.css

351 ms

select2-krajee-bs3.min.css

select2-krajee-bs3.min.css

361 ms

conversion.js

conversion.js

93 ms

api.js

api.js

39 ms

jquery.js

jquery.js

562 ms

bootstrap.js

bootstrap.js

334 ms

owl.carousel.min.js

owl.carousel.min.js

438 ms

yii.js

yii.js

439 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

438 ms

datepicker-kv.min.js

datepicker-kv.min.js

437 ms

kv-widgets.min.js

kv-widgets.min.js

438 ms

yii.activeForm.js

yii.activeForm.js

560 ms

ajax-modal-popup.js

ajax-modal-popup.js

560 ms

select2.full.min.js

select2.full.min.js

673 ms

select2-krajee.min.js

select2-krajee.min.js

558 ms

cookieconsent.min.js

cookieconsent.min.js

558 ms

yii.validation.js

yii.validation.js

723 ms

gtm.js

gtm.js

223 ms

fbevents.js

fbevents.js

153 ms

hotjar-1413357.js

hotjar-1413357.js

301 ms

logo_puurenkuur_en.png

logo_puurenkuur_en.png

436 ms

phone-icon.svg

phone-icon.svg

436 ms

en.jpg

en.jpg

435 ms

nl.jpg

nl.jpg

435 ms

be.jpg

be.jpg

480 ms

button_close_gold.svg

button_close_gold.svg

557 ms

check_icon_gold.svg

check_icon_gold.svg

560 ms

14b8ca172e565de1ff3cba67544a7c6a.webp

14b8ca172e565de1ff3cba67544a7c6a.webp

560 ms

f35b2e2fc5b47f8fae9daa3791e25993.webp

f35b2e2fc5b47f8fae9daa3791e25993.webp

571 ms

50a815e2eb760ece8c6e95f7fa32011c.webp

50a815e2eb760ece8c6e95f7fa32011c.webp

584 ms

82a1bea0122bcf2e9fc39143179e2306.webp

82a1bea0122bcf2e9fc39143179e2306.webp

614 ms

0cf2e7221c6788a8216aab409a478406.webp

0cf2e7221c6788a8216aab409a478406.webp

651 ms

promotion_empty_image.png

promotion_empty_image.png

571 ms

5418bcebd5a3d87542e85762c60c4038.jpg

5418bcebd5a3d87542e85762c60c4038.jpg

575 ms

6593c45408e9d4e46517540a7ae0d988.jpg

6593c45408e9d4e46517540a7ae0d988.jpg

658 ms

732432178579df72f3a6b715ea398878.jpg

732432178579df72f3a6b715ea398878.jpg

741 ms

marleen_van_griensven.webp

marleen_van_griensven.webp

663 ms

blue_plant.svg

blue_plant.svg

676 ms

seen_in_grazia.webp

seen_in_grazia.webp

700 ms

seen_in_red.webp

seen_in_red.webp

735 ms

seen_in_telegraaf.webp

seen_in_telegraaf.webp

742 ms

seen_in_happinez.webp

seen_in_happinez.webp

750 ms

analytics.js

analytics.js

195 ms

seen_in_vogue.webp

seen_in_vogue.webp

728 ms

154 ms

seen_in_tatler.webp

seen_in_tatler.webp

649 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

158 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

175 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

240 ms

recaptcha__en.js

recaptcha__en.js

172 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

759 ms

seen_in_ft.webp

seen_in_ft.webp

681 ms

whatsapp_logo_2.png

whatsapp_logo_2.png

682 ms

arrow-icon-down.svg

arrow-icon-down.svg

693 ms

loading-plugin.gif

loading-plugin.gif

687 ms

collect

collect

97 ms

js

js

123 ms

arrow-icon-gold-down.svg

arrow-icon-gold-down.svg

610 ms

arrow-icon-black-down.svg

arrow-icon-black-down.svg

653 ms

date-icon-black.svg

date-icon-black.svg

655 ms

bg-plant-big.svg

bg-plant-big.svg

635 ms

footer_logos.png

footer_logos.png

662 ms

86 ms

modules.84f80a92c39bbd76564a.js

modules.84f80a92c39bbd76564a.js

138 ms

collect

collect

164 ms

js

js

119 ms

ga-audiences

ga-audiences

81 ms

2d250c34e68d2748b063245073e27a8b.webp

2d250c34e68d2748b063245073e27a8b.webp

588 ms

5670a68825205031e26e8278c87b1f8c.webp

5670a68825205031e26e8278c87b1f8c.webp

519 ms

c845c488892cf99eff95759a01ea66ba.webp

c845c488892cf99eff95759a01ea66ba.webp

786 ms

fa3b8c5300677aec570a26c37bd47cc7.webp

fa3b8c5300677aec570a26c37bd47cc7.webp

616 ms

8876b7a8bb3499ab15d9484d90d74f14.webp

8876b7a8bb3499ab15d9484d90d74f14.webp

724 ms

light-floating.css

light-floating.css

145 ms

Accessibility Review

pureandcure.com accessibility score

80

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 input fields do not have accessible names

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

Image elements do not have [alt] attributes

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

Best Practices

pureandcure.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pureandcure.com SEO score

72

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

pureandcure.com

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