Tools & Wizards About Us
pellarin.de screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pellarin.de

Willkommen in der Praxis für Mund-, Kiefer- und Zahnheilkunde | Zahnarztpraxis

Page Load Speed

4 sec in total

First Response

944 ms

Resources Loaded

2.9 sec

Page Rendered

164 ms

pellarin.de screenshot

About Website

Visit pellarin.de now to see the best up-to-date Pellarin content and also check out these interesting facts you probably never knew about pellarin.de

Ganzheitliche Praxis für Mund-, Kiefer- und Zahnheilkunde und Zahnarztpraxis von Dr. med. Markus Pellarin Facharzt für Mund,- Kiefer und Gesichtschirurgie

Visit pellarin.de

Key Findings

We analyzed Pellarin.de page load time and found that the first response time was 944 ms and then it took 3 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

pellarin.de performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

zahnpraxis.center

944 ms

joomla-alert.min.css

190 ms

jcemediabox.min.css

289 ms

content.min.css

287 ms

jquery.min.js

382 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pellarin.de, 3% (2 requests) were made to App.eu.usercentrics.eu and 3% (2 requests) were made to Cdn1.jameda-elements.de. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Zahnpraxis.center.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.8 kB (6%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pellarin.de main page is 1.3 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. Javascripts take 732.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 49.1 kB

  • Original 63.2 kB
  • After minification 58.1 kB
  • After compression 14.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. 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 49.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 19.0 kB

  • Original 411.8 kB
  • After minification 392.7 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. Pellarin images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 7.0 kB

  • Original 732.0 kB
  • After minification 731.9 kB
  • After compression 725.0 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

-8%

Potential reduce by 4.7 kB

  • Original 61.9 kB
  • After minification 61.9 kB
  • After compression 57.2 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. Pellarin.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (79%)

Requests Now

62

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zahnpraxis.center

zahnpraxis.center

944 ms

joomla-alert.min.css

joomla-alert.min.css

190 ms

jcemediabox.min.css

jcemediabox.min.css

289 ms

content.min.css

content.min.css

287 ms

jquery.min.js

jquery.min.js

382 ms

jquery-noconflict.min.js

jquery-noconflict.min.js

287 ms

menu-es5.min.js

menu-es5.min.js

391 ms

core.min.js

core.min.js

392 ms

webcomponents-bundle.min.js

webcomponents-bundle.min.js

478 ms

bootstrap-es5.min.js

bootstrap-es5.min.js

628 ms

messages-es5.min.js

messages-es5.min.js

478 ms

joomla-hidden-mail-es5.min.js

joomla-hidden-mail-es5.min.js

478 ms

alert.min.js

alert.min.js

479 ms

button.min.js

button.min.js

575 ms

carousel.min.js

carousel.min.js

575 ms

collapse.min.js

collapse.min.js

575 ms

dropdown.min.js

dropdown.min.js

575 ms

modal.min.js

modal.min.js

672 ms

offcanvas.min.js

offcanvas.min.js

671 ms

popover.min.js

popover.min.js

671 ms

scrollspy.min.js

scrollspy.min.js

671 ms

tab.min.js

tab.min.js

725 ms

toast.min.js

toast.min.js

767 ms

joomla-hidden-mail.min.js

joomla-hidden-mail.min.js

766 ms

messages.min.js

messages.min.js

766 ms

jcemediabox.min.js

jcemediabox.min.js

861 ms

jquery-ui-addons.js

jquery-ui-addons.js

884 ms

bootstrap-default-min.css

bootstrap-default-min.css

824 ms

bootstrap-responsive.css

bootstrap-responsive.css

864 ms

s5_flex_menu-min.js

s5_flex_menu-min.js

865 ms

custom-script.js

custom-script.js

863 ms

s5_flex_menu.css

s5_flex_menu.css

922 ms

general.css

general.css

1163 ms

template_default.css

template_default.css

957 ms

template.css

template.css

958 ms

com_content.css

com_content.css

960 ms

loader.js

loader.js

45 ms

uc-block.bundle.js

uc-block.bundle.js

47 ms

101 ms

editor.css

editor.css

893 ms

thirdparty.css

thirdparty.css

836 ms

s5_responsive_bars-min.css

s5_responsive_bars-min.css

770 ms

s5_responsive_hide_classes-min.css

s5_responsive_hide_classes-min.css

769 ms

s5_responsive.css

s5_responsive.css

770 ms

smartslider.min.css

smartslider.min.css

693 ms

n2.min.js

n2.min.js

735 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

963 ms

ss-simple.min.js

ss-simple.min.js

690 ms

smartslider-backgroundanimation.min.js

smartslider-backgroundanimation.min.js

878 ms

w-arrow-image.min.js

w-arrow-image.min.js

704 ms

w-bullet.min.js

w-bullet.min.js

835 ms

s5_responsive_mobile_bar-min.js

s5_responsive_mobile_bar-min.js

740 ms

search_light.png

search_light.png

155 ms

menu_light.png

menu_light.png

175 ms

logo.jpg

logo.jpg

188 ms

Home-V3.jpg

Home-V3.jpg

500 ms

behandlungszimmer1.jpg

behandlungszimmer1.jpg

348 ms

Eingang.jpg

Eingang.jpg

371 ms

Empfang.jpg

Empfang.jpg

277 ms

Wartezimmer.jpg

Wartezimmer.jpg

281 ms

bundle_legacy.js

bundle_legacy.js

17 ms

bw-small-bg.png

bw-small-bg.png

14 ms

s5_scroll_arrow.png

s5_scroll_arrow.png

111 ms

languages.json

languages.json

173 ms

Accessibility Review

pellarin.de accessibility score

81

Accessibility Issues

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

pellarin.de best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pellarin.de SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pellarin.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Pellarin.de 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

pellarin.de

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