Report Summary

  • 25

    Performance

    Renders faster than
    44% 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.al

Oral health care from Switzerland | CURAPROX-Shop USA

Page Load Speed

7.2 sec in total

First Response

416 ms

Resources Loaded

3.8 sec

Page Rendered

2.9 sec

curaprox.al screenshot

About Website

Welcome to curaprox.al homepage info - get ready to check CURAPROX best content right away, or after learning these important things about curaprox.al

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

Visit curaprox.al

Key Findings

We analyzed Curaprox.al page load time and found that the first response time was 416 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

curaprox.al performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,440 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

curaprox.us

416 ms

gtm.js

433 ms

theme-877019281.css

114 ms

vxm1nqf.css

430 ms

jquery-1.11.0.min.js

87 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Curaprox.al, 14% (8 requests) were made to Use.typekit.net and 3% (2 requests) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Curaprox.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.3 kB (8%)

Content Size

1.7 MB

After Optimization

1.6 MB

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

HTML Optimization

-82%

Potential reduce by 86.6 kB

  • Original 105.8 kB
  • After minification 83.6 kB
  • After compression 19.2 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 22.2 kB, which is 21% 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 86.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 66 B

  • Original 1.3 MB
  • After minification 1.3 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

-0%

Potential reduce by 244 B

  • Original 116.0 kB
  • After minification 116.0 kB
  • After compression 115.7 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 49.4 kB

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

Requests Breakdown

Number of requests can be reduced by 12 (24%)

Requests Now

49

After Optimization

37

The browser has sent 49 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Curaprox.al 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 Curaprox.al 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

Open Graph data is detected on the main page of CURAPROX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: