Tools & Wizards About Us
parfum.bayern screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

parfum.bayern

Dufte Düfte von parfüm.bayern - Armaf Parfums von parfüm.bayern

Page Load Speed

4.2 sec in total

First Response

322 ms

Resources Loaded

3 sec

Page Rendered

798 ms

parfum.bayern screenshot

About Website

Click here to check amazing Parfum content. Otherwise, check out these important facts you probably never knew about parfum.bayern

Parfüm.bayern - Dufte Düfte zum besten Preis von Alexandria Fragrances, Armaf Parfums & Jacques Battini, AJMAL, Khalis

Visit parfum.bayern

Key Findings

We analyzed Parfum.bayern page load time and found that the first response time was 322 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

parfum.bayern performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

parfum.bayern

322 ms

www.xn--parfm-nva.bayern

660 ms

141 ms

package-sf.css

335 ms

package-sf.js

700 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Parfum.bayern, 1% (1 request) were made to Parfum.bayern. The less responsive or slowest element that took the longest time to load (801 ms) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 28.6 kB (12%)

Content Size

233.4 kB

After Optimization

204.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Parfum.bayern main page is 233.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 107.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 17.3 kB

  • Original 21.4 kB
  • After minification 21.0 kB
  • After compression 4.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 17.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 107.8 kB
  • After minification 107.8 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. Parfum images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 6.5 kB

  • Original 51.1 kB
  • After minification 50.7 kB
  • After compression 44.6 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 6.5 kB or 13% of the original size.

CSS Optimization

-9%

Potential reduce by 4.8 kB

  • Original 53.1 kB
  • After minification 53.1 kB
  • After compression 48.3 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. Parfum.bayern has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 57 (88%)

Requests Now

65

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

parfum.bayern

parfum.bayern

322 ms

www.xn--parfm-nva.bayern

www.xn--parfm-nva.bayern

660 ms

141 ms

package-sf.css

package-sf.css

335 ms

package-sf.js

package-sf.js

700 ms

StorefrontStyle_1360.css

StorefrontStyle_1360.css

510 ms

style-ie.css

style-ie.css

112 ms

de-DE.js

de-DE.js

119 ms

EUR.js

EUR.js

124 ms

string.js

string.js

121 ms

legacy.js

legacy.js

152 ms

tools.js

tools.js

174 ms

constants.js

constants.js

186 ms

browser.js

browser.js

180 ms

scope.js

scope.js

232 ms

json.js

json.js

255 ms

base64.js

base64.js

263 ms

inject-sec-token.js

inject-sec-token.js

274 ms

data.js

data.js

255 ms

disable-selection.js

disable-selection.js

299 ms

focusable.js

focusable.js

322 ms

form.js

form.js

330 ms

ie.js

ie.js

336 ms

keycode.js

keycode.js

345 ms

labels.js

labels.js

352 ms

jquery-1-7.js

jquery-1-7.js

390 ms

plugin.js

plugin.js

414 ms

safe-active-element.js

safe-active-element.js

422 ms

safe-blur.js

safe-blur.js

432 ms

scroll-parent.js

scroll-parent.js

443 ms

tabbable.js

tabbable.js

447 ms

unique-id.js

unique-id.js

487 ms

version.js

version.js

507 ms

mouse.js

mouse.js

515 ms

dialog.js

dialog.js

528 ms

tabs.js

tabs.js

533 ms

slider.js

slider.js

543 ms

$pub.js

$pub.js

578 ms

cookie.js

cookie.js

600 ms

class.js

class.js

607 ms

mime.js

mime.js

629 ms

$dict.js

$dict.js

616 ms

$tmpl.js

$tmpl.js

595 ms

core.js

core.js

618 ms

support.js

support.js

640 ms

load.js

load.js

647 ms

touch.js

touch.js

620 ms

version.js

version.js

607 ms

validate.js

validate.js

610 ms

storage.js

storage.js

625 ms

de_epages.js

de_epages.js

607 ms

cookiemessage.js

cookiemessage.js

585 ms

$ready.js

$ready.js

594 ms

energylabel.js

energylabel.js

605 ms

utf8.js

utf8.js

599 ms

Background_bokeh.jpg

Background_bokeh.jpg

801 ms

button.js

button.js

370 ms

draggable.js

draggable.js

370 ms

resizable.js

resizable.js

398 ms

escape-selector.js

escape-selector.js

397 ms

dict.de.json

dict.de.json

322 ms

simpledialog.js

simpledialog.js

171 ms

button.js

button.js

103 ms

draggable.js

draggable.js

98 ms

resizable.js

resizable.js

116 ms

controlgroup.js

controlgroup.js

111 ms

checkboxradio.js

checkboxradio.js

111 ms

Accessibility Review

parfum.bayern accessibility score

74

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.

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

parfum.bayern 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

Page has valid source maps

SEO Factors

parfum.bayern SEO score

85

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 Parfum.bayern 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 Parfum.bayern 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

parfum.bayern

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