5.6 sec in total
379 ms
4.6 sec
619 ms
Click here to check amazing CURAPROX content. Otherwise, check out these important facts you probably never knew about curaprox.co.uk
Brushing your teeth with Curaprox is gentle, joyful and healthy... even when whitening. Find out more…
Visit curaprox.co.ukWe analyzed Curaprox.co.uk page load time and found that the first response time was 379 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
curaprox.co.uk performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.5 s
19/100
25%
Value8.9 s
15/100
10%
Value1,130 ms
22/100
30%
Value0.067
97/100
15%
Value14.8 s
8/100
10%
379 ms
786 ms
592 ms
55 ms
142 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Curaprox.co.uk, 85% (41 requests) were made to Curaprox.com and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (905 ms) relates to the external source Curaprox.com.
Page size can be reduced by 295.2 kB (27%)
1.1 MB
802.5 kB
In fact, the total size of Curaprox.co.uk main page is 1.1 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. 55% of websites need less resources to load. Images take 709.1 kB which makes up the majority of the site volume.
Potential reduce by 33.7 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 33.7 kB or 83% of the original size.
Potential reduce by 15.9 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. CURAPROX images are well optimized though.
Potential reduce by 137.8 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.
Potential reduce by 107.8 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.co.uk needs all CSS files to be minified and compressed as it can save up to 107.8 kB or 87% of the original size.
Number of requests can be reduced by 13 (32%)
41
28
The browser has sent 41 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.
curaprox.co.uk
379 ms
gb-en
786 ms
gb-en
592 ms
css
55 ms
owl.carousel.min.css
142 ms
animate.min.css
282 ms
slicknav.css
349 ms
style.css
366 ms
featherlight.min.css
368 ms
style.css
467 ms
picturefill.min.js
357 ms
jquery.min.js
526 ms
jquery.slicknav.min.js
490 ms
owl.carousel.min.js
502 ms
featherlight.min.js
502 ms
init.js
506 ms
ga.js
28 ms
piwik.js
590 ms
__utm.gif
14 ms
bg_dotted_2.png
254 ms
menuTechDivider.gif
241 ms
curaprox_logo.gif
241 ms
banner_biw_900x240.jpg
374 ms
cs5460_spot_uk.jpg
421 ms
banner_smart_092014_1.jpg
295 ms
banner_smart_092014_2.jpg
456 ms
banner_smart_092014_3.jpg
458 ms
70807_interview_maurer_teaser.jpg
455 ms
48602_interview_fcz_teaser.jpg
528 ms
82623_interview_teaser_saxer.jpg
512 ms
22867_teaser_interview_1.jpg
584 ms
20237_banner_laecheln_2.jpg
690 ms
48424_banner_laecheln_3.jpg
689 ms
49366_banner_laecheln_0.jpg
595 ms
20229_banner_laecheln_1.jpg
654 ms
48444_banner_laecheln_5.jpg
665 ms
59869_banner_laecheln_4.jpg
722 ms
59921_banner_laecheln_6.jpg
830 ms
48458_banner_laecheln_7.jpg
791 ms
485990_ueli_breitschmid.jpg
905 ms
Z-FsjIS3sPD5Zt6xiv44Ry3USBnSvpkopQaUR-2r7iU.ttf
34 ms
ShL_W4dvX9R2li-OgANwuA.ttf
210 ms
8-PQNacfI9IhpgehJGCuGC3USBnSvpkopQaUR-2r7iU.ttf
213 ms
icomoon.ttf
802 ms
boxEmpty0.png
600 ms
boxFull0.gif
634 ms
boxEmpty1.png
707 ms
boxFull1.gif
734 ms
curaprox.co.uk accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
curaprox.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
curaprox.co.uk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Curaprox.co.uk 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.co.uk 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.
curaprox.co.uk
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: