Tools & Wizards About Us
piascledine.co.za screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

piascledine.co.za

Piascledine – treatment for the osteoarthritis of the knee and hip

Page Load Speed

4.5 sec in total

First Response

172 ms

Resources Loaded

4.1 sec

Page Rendered

228 ms

piascledine.co.za screenshot

About Website

Visit piascledine.co.za now to see the best up-to-date Piascledine content and also check out these interesting facts you probably never knew about piascledine.co.za

Piascledine 300 is used to treat the symptoms of the knee and hip osteoarthritis. PIASCLEDINE® belongs to the class of “SYSADOA” (symptomatic slow-acting drugs in osteoarthritis).

Visit piascledine.co.za

Key Findings

We analyzed Piascledine.co.za page load time and found that the first response time was 172 ms and then it took 4.3 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

piascledine.co.za performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

piascledine.co.za

172 ms

www.piascledine.co.za

149 ms

www.piascledine.co.za

1382 ms

js

52 ms

slick.css

88 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 95% of them (148 requests) were addressed to the original Piascledine.co.za, 2% (3 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Piascledine.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 794.1 kB (34%)

Content Size

2.4 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piascledine.co.za main page is 2.4 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.4 kB

  • Original 35.5 kB
  • After minification 33.5 kB
  • After compression 7.1 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 28.4 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 112.8 kB

  • Original 1.4 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. Piascledine images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 417.8 kB

  • Original 596.3 kB
  • After minification 537.3 kB
  • After compression 178.5 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 417.8 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 235.1 kB

  • Original 281.5 kB
  • After minification 225.9 kB
  • After compression 46.5 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. Piascledine.co.za needs all CSS files to be minified and compressed as it can save up to 235.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 132 (89%)

Requests Now

148

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

piascledine.co.za

piascledine.co.za

172 ms

www.piascledine.co.za

www.piascledine.co.za

149 ms

www.piascledine.co.za

www.piascledine.co.za

1382 ms

js

js

52 ms

slick.css

slick.css

88 ms

slick.module.css

slick.module.css

170 ms

core.css

core.css

263 ms

controlgroup.css

controlgroup.css

259 ms

checkboxradio.css

checkboxradio.css

264 ms

resizable.css

resizable.css

261 ms

button.css

button.css

263 ms

dialog.css

dialog.css

264 ms

align.module.css

align.module.css

341 ms

fieldgroup.module.css

fieldgroup.module.css

342 ms

container-inline.module.css

container-inline.module.css

344 ms

clearfix.module.css

clearfix.module.css

345 ms

details.module.css

details.module.css

346 ms

hidden.module.css

hidden.module.css

350 ms

item-list.module.css

item-list.module.css

418 ms

js.module.css

js.module.css

419 ms

nowrap.module.css

nowrap.module.css

422 ms

position-container.module.css

position-container.module.css

421 ms

progress.module.css

progress.module.css

424 ms

reset-appearance.module.css

reset-appearance.module.css

428 ms

resize.module.css

resize.module.css

496 ms

sticky-header.module.css

sticky-header.module.css

496 ms

system-status-counter.css

system-status-counter.css

498 ms

system-status-report-counters.css

system-status-report-counters.css

501 ms

system-status-report-general-info.css

system-status-report-general-info.css

502 ms

tablesort.module.css

tablesort.module.css

505 ms

tree-child.module.css

tree-child.module.css

572 ms

views.module.css

views.module.css

576 ms

blazy.css

blazy.css

579 ms

blazy.loading.css

blazy.loading.css

583 ms

theme.css

theme.css

649 ms

slick-theme.css

slick-theme.css

581 ms

slick.theme.css

slick.theme.css

654 ms

slick.theme--full.css

slick.theme--full.css

653 ms

slick.theme--fullwidth.css

slick.theme--fullwidth.css

655 ms

styles.css

styles.css

795 ms

js

js

55 ms

analytics.js

analytics.js

21 ms

font-awesome.css

font-awesome.css

648 ms

collect

collect

41 ms

blazy.polyfill.min.js

blazy.polyfill.min.js

569 ms

jquery.min.js

jquery.min.js

625 ms

underscore-min.js

underscore-min.js

552 ms

blazy.classlist.min.js

blazy.classlist.min.js

477 ms

blazy.promise.min.js

blazy.promise.min.js

552 ms

blazy.raf.min.js

blazy.raf.min.js

552 ms

nodelist.foreach.js

nodelist.foreach.js

558 ms

element.matches.js

element.matches.js

555 ms

object.assign.js

object.assign.js

554 ms

css.escape.js

css.escape.js

555 ms

once.min.js

once.min.js

554 ms

jquery.once.min.js

jquery.once.min.js

559 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

610 ms

drupal.js

drupal.js

544 ms

drupal.init.js

drupal.init.js

543 ms

debounce.js

debounce.js

548 ms

version-min.js

version-min.js

554 ms

data-min.js

data-min.js

554 ms

disable-selection-min.js

disable-selection-min.js

610 ms

focusable-min.js

focusable-min.js

544 ms

form-min.js

form-min.js

549 ms

ie-min.js

ie-min.js

551 ms

jquery-patch-min.js

jquery-patch-min.js

551 ms

keycode-min.js

keycode-min.js

552 ms

plugin-min.js

plugin-min.js

611 ms

safe-active-element-min.js

safe-active-element-min.js

544 ms

safe-blur-min.js

safe-blur-min.js

546 ms

scroll-parent-min.js

scroll-parent-min.js

547 ms

unique-id-min.js

unique-id-min.js

547 ms

widget-min.js

widget-min.js

548 ms

controlgroup-min.js

controlgroup-min.js

546 ms

form-reset-mixin-min.js

form-reset-mixin-min.js

541 ms

labels-min.js

labels-min.js

545 ms

mouse-min.js

mouse-min.js

546 ms

checkboxradio-min.js

checkboxradio-min.js

474 ms

draggable-min.js

draggable-min.js

477 ms

resizable-min.js

resizable-min.js

539 ms

css2

css2

29 ms

button-min.js

button-min.js

471 ms

dialog-min.js

dialog-min.js

469 ms

dblazy.min.js

dblazy.min.js

471 ms

blazy.dataset.min.js

blazy.dataset.min.js

479 ms

blazy.viewport.min.js

blazy.viewport.min.js

474 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

33 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

33 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

41 ms

blazy.dom.min.js

blazy.dom.min.js

461 ms

blazy.xlazy.min.js

blazy.xlazy.min.js

464 ms

blazy.observer.min.js

blazy.observer.min.js

466 ms

blazy.loading.min.js

blazy.loading.min.js

464 ms

blazy.webp.min.js

blazy.webp.min.js

467 ms

blazy.base.min.js

blazy.base.min.js

461 ms

blazy.min.js

blazy.min.js

471 ms

bio.min.js

bio.min.js

478 ms

jquery.easing.min.js

jquery.easing.min.js

471 ms

slick.min.js

slick.min.js

470 ms

bio.media.min.js

bio.media.min.js

471 ms

blazy.drupal.min.js

blazy.drupal.min.js

472 ms

blazy.load.min.js

blazy.load.min.js

471 ms

index.umd.min.js

index.umd.min.js

477 ms

google_analytics.js

google_analytics.js

473 ms

drupal.bootstrap.js

drupal.bootstrap.js

469 ms

attributes.js

attributes.js

474 ms

theme.js

theme.js

474 ms

affix.js

affix.js

477 ms

alert.js

alert.js

476 ms

button.js

button.js

472 ms

carousel.js

carousel.js

472 ms

collapse.js

collapse.js

475 ms

dropdown.js

dropdown.js

474 ms

modal.js

modal.js

474 ms

tooltip.js

tooltip.js

474 ms

popover.js

popover.js

472 ms

scrollspy.js

scrollspy.js

471 ms

tab.js

tab.js

476 ms

transition.js

transition.js

472 ms

popover.js

popover.js

475 ms

tooltip.js

tooltip.js

471 ms

slick.load.min.js

slick.load.min.js

471 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

473 ms

height-same.js

height-same.js

469 ms

jumpto.js

jumpto.js

470 ms

progress.js

progress.js

473 ms

progress.js

progress.js

473 ms

jquery.once.bc.js

jquery.once.bc.js

471 ms

ajax.js

ajax.js

473 ms

ajax.js

ajax.js

472 ms

displace.js

displace.js

470 ms

jquery.tabbable.shim.js

jquery.tabbable.shim.js

474 ms

position.js

position.js

473 ms

modal.js

modal.js

471 ms

dialog.js

dialog.js

471 ms

modal.jquery.ui.bridge.js

modal.jquery.ui.bridge.js

472 ms

dialog.js

dialog.js

472 ms

dialog.position.js

dialog.position.js

475 ms

dialog.ajax.js

dialog.ajax.js

469 ms

dialog.ajax.js

dialog.ajax.js

468 ms

slick.woff

slick.woff

524 ms

flexslider-icon.woff

flexslider-icon.woff

517 ms

austell_top.png

austell_top.png

516 ms

logo.png

logo.png

469 ms

sublogo.png

sublogo.png

471 ms

sl1.jpg

sl1.jpg

684 ms

sl2.jpg

sl2.jpg

680 ms

sl3.jpg

sl3.jpg

749 ms

piascledine-and-osteoathritis-reduces-pain_0.jpg

piascledine-and-osteoathritis-reduces-pain_0.jpg

481 ms

stiff-and-painfull%20joints.jpg

stiff-and-painfull%20joints.jpg

540 ms

faqs-slows-disease-progression_0.jpg

faqs-slows-disease-progression_0.jpg

477 ms

expanscience_logo.png

expanscience_logo.png

498 ms

newsletter_send.png

newsletter_send.png

551 ms

marker.png

marker.png

565 ms

ajax-loader.gif

ajax-loader.gif

255 ms

Accessibility Review

piascledine.co.za 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

[role]s do not have all required [aria-*] 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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

piascledine.co.za best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

piascledine.co.za SEO score

77

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 Piascledine.co.za 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 Piascledine.co.za 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

piascledine.co.za

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