Tools & Wizards About Us
curaprox.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

curaprox.com

Oral health care from Switzerland | CURAPROX-Shop USA

Page Load Speed

5.3 sec in total

First Response

398 ms

Resources Loaded

4.3 sec

Page Rendered

537 ms

curaprox.com screenshot

About Website

Click here to check amazing CURAPROX content for United Arab Emirates. Otherwise, check out these important facts you probably never knew about curaprox.com

Brushing your teeth with Curaprox is gentle, joyful and healthy... even when whitening. Find out more…

Visit curaprox.com

Key Findings

We analyzed Curaprox.com page load time and found that the first response time was 398 ms and then it took 4.9 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

curaprox.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

curaprox.com

398 ms

curaprox.com

1346 ms

css

59 ms

owl.carousel.min.css

1017 ms

animate.min.css

1064 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 89% of them (48 requests) were addressed to the original Curaprox.com, 6% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Curaprox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.1 kB (23%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 41.7 kB

  • Original 50.9 kB
  • After minification 50.0 kB
  • After compression 9.3 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 41.7 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 63.4 kB

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

JavaScript Optimization

-62%

Potential reduce by 137.8 kB

  • Original 223.9 kB
  • After minification 223.4 kB
  • After compression 86.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 137.8 kB or 62% of the original size.

CSS Optimization

-87%

Potential reduce by 108.2 kB

  • Original 124.6 kB
  • After minification 113.1 kB
  • After compression 16.4 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. Curaprox.com needs all CSS files to be minified and compressed as it can save up to 108.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (27%)

Requests Now

48

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

curaprox.com

curaprox.com

398 ms

curaprox.com

curaprox.com

1346 ms

css

css

59 ms

owl.carousel.min.css

owl.carousel.min.css

1017 ms

animate.min.css

animate.min.css

1064 ms

slicknav.css

slicknav.css

1068 ms

style.css

style.css

1066 ms

featherlight.min.css

featherlight.min.css

1071 ms

style.css

style.css

1052 ms

picturefill.min.js

picturefill.min.js

1181 ms

jquery.min.js

jquery.min.js

1305 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

1223 ms

owl.carousel.min.js

owl.carousel.min.js

1193 ms

featherlight.min.js

featherlight.min.js

1201 ms

init.js

init.js

1223 ms

ga.js

ga.js

69 ms

piwik.js

piwik.js

240 ms

__utm.gif

__utm.gif

12 ms

bg_dotted_2.png

bg_dotted_2.png

231 ms

menuTechDivider.gif

menuTechDivider.gif

224 ms

curaprox_logo.gif

curaprox_logo.gif

224 ms

biw_1.jpg

biw_1.jpg

405 ms

biw_2_en.jpg

biw_2_en.jpg

422 ms

biw_3_en.jpg

biw_3_en.jpg

427 ms

curaprox_logo_mind_the_gap.jpg

curaprox_logo_mind_the_gap.jpg

336 ms

banner_cps_prime_092014_1.jpg

banner_cps_prime_092014_1.jpg

427 ms

banner_cps_prime_092014_2.jpg

banner_cps_prime_092014_2.jpg

432 ms

banner_cps_prime_092014_3.jpg

banner_cps_prime_092014_3.jpg

551 ms

70807_interview_maurer_teaser.jpg

70807_interview_maurer_teaser.jpg

539 ms

42961_interview_warrer_teaser.jpg

42961_interview_warrer_teaser.jpg

560 ms

48602_interview_fcz_teaser.jpg

48602_interview_fcz_teaser.jpg

552 ms

50024_interview_judith_teaser.jpg

50024_interview_judith_teaser.jpg

640 ms

03984_interview_muetsch_teaser.jpg

03984_interview_muetsch_teaser.jpg

653 ms

71564_interview_laura_teaser.jpg

71564_interview_laura_teaser.jpg

663 ms

48424_banner_laecheln_3.jpg

48424_banner_laecheln_3.jpg

769 ms

59869_banner_laecheln_4.jpg

59869_banner_laecheln_4.jpg

672 ms

20237_banner_laecheln_2.jpg

20237_banner_laecheln_2.jpg

682 ms

20229_banner_laecheln_1.jpg

20229_banner_laecheln_1.jpg

776 ms

49366_banner_laecheln_0.jpg

49366_banner_laecheln_0.jpg

800 ms

48444_banner_laecheln_5.jpg

48444_banner_laecheln_5.jpg

796 ms

59921_banner_laecheln_6.jpg

59921_banner_laecheln_6.jpg

809 ms

48458_banner_laecheln_7.jpg

48458_banner_laecheln_7.jpg

817 ms

60581_banner_laecheln_speichel.jpg

60581_banner_laecheln_speichel.jpg

932 ms

60423_banner_laecheln_plaque.jpg

60423_banner_laecheln_plaque.jpg

920 ms

1686056_ueli_breitschmid.jpg

1686056_ueli_breitschmid.jpg

1024 ms

Z-FsjIS3sPD5Zt6xiv44R73hpw3pgy2gAi-Ip7WPMi0.woff

Z-FsjIS3sPD5Zt6xiv44R73hpw3pgy2gAi-Ip7WPMi0.woff

181 ms

a4UjYmRBuLgi7ce4oxgshgLUuEpTyoUstqEm5AMlJo4.woff

a4UjYmRBuLgi7ce4oxgshgLUuEpTyoUstqEm5AMlJo4.woff

199 ms

8-PQNacfI9IhpgehJGCuGL3hpw3pgy2gAi-Ip7WPMi0.woff

8-PQNacfI9IhpgehJGCuGL3hpw3pgy2gAi-Ip7WPMi0.woff

210 ms

icomoon.ttf

icomoon.ttf

921 ms

schweiz.jpg

schweiz.jpg

908 ms

boxEmpty0.png

boxEmpty0.png

765 ms

boxFull0.gif

boxFull0.gif

865 ms

boxEmpty1.png

boxEmpty1.png

876 ms

boxFull1.gif

boxFull1.gif

877 ms

Accessibility Review

curaprox.com accessibility score

73

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

Links do not have a discernible name

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

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

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

curaprox.com 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

Missing source maps for large first-party JavaScript

SEO Factors

curaprox.com SEO score

91

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

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

curaprox.com

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