Tools & Wizards About Us
pheromone.de screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 63

    SEO

    Google-friendlier than
    24% of websites

pheromone.de

Pheromone.de - Pheromone günstig im Internet kaufen

Page Load Speed

2.6 sec in total

First Response

252 ms

Resources Loaded

2.1 sec

Page Rendered

270 ms

pheromone.de screenshot

About Website

Welcome to pheromone.de homepage info - get ready to check Pheromone best content for Germany right away, or after learning these important things about pheromone.de

In unserem Pheromoneversand finden Sie hochwertige Pheromonprodukte, die seit Jahren bei unseren Kunden funktionieren.

Visit pheromone.de

Key Findings

We analyzed Pheromone.de page load time and found that the first response time was 252 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pheromone.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.219

57/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

pheromone.de

252 ms

www.pheromone.de

637 ms

jquery.min.js

29 ms

home.css

109 ms

controller.js

218 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 69% of them (35 requests) were addressed to the original Pheromone.de, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (637 ms) belongs to the original domain Pheromone.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.5 kB (35%)

Content Size

421.3 kB

After Optimization

273.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pheromone.de main page is 421.3 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. 50% of websites need less resources to load. Javascripts take 197.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 71.7 kB

  • Original 89.3 kB
  • After minification 82.1 kB
  • After compression 17.6 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 71.7 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 850 B

  • Original 107.6 kB
  • After minification 106.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. Pheromone images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 64.1 kB

  • Original 197.6 kB
  • After minification 196.4 kB
  • After compression 133.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 64.1 kB or 32% of the original size.

CSS Optimization

-40%

Potential reduce by 10.8 kB

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 16.0 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. Pheromone.de needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (64%)

Requests Now

47

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pheromone.de

pheromone.de

252 ms

www.pheromone.de

www.pheromone.de

637 ms

jquery.min.js

jquery.min.js

29 ms

home.css

home.css

109 ms

controller.js

controller.js

218 ms

ion.rangeSlider.min.js

ion.rangeSlider.min.js

309 ms

slick.min.js

slick.min.js

423 ms

jquery.leanModal.min.js

jquery.leanModal.min.js

316 ms

validetta.min.js

validetta.min.js

323 ms

jquery.elevateZoom-3.0.8.min.js

jquery.elevateZoom-3.0.8.min.js

463 ms

jquery.izilla.touchMenuHover.min.js

jquery.izilla.touchMenuHover.min.js

323 ms

normalize.css

normalize.css

415 ms

slick.css

slick.css

425 ms

style.css

style.css

488 ms

ion.rangeSlider.css

ion.rangeSlider.css

435 ms

ion.rangeSlider.skinNice.css

ion.rangeSlider.skinNice.css

522 ms

validetta.min.css

validetta.min.css

528 ms

js

js

64 ms

conversion.js

conversion.js

89 ms

trad.js

trad.js

74 ms

3c7b9fdcddd4ecfec384c48b0bab77b4.js

3c7b9fdcddd4ecfec384c48b0bab77b4.js

489 ms

js

js

62 ms

js

js

201 ms

analytics.js

analytics.js

171 ms

bgr_pheromone.gif

bgr_pheromone.gif

185 ms

bgr_3.gif

bgr_3.gif

185 ms

icon.gif

icon.gif

185 ms

logo-r.gif

logo-r.gif

184 ms

red-bag.png

red-bag.png

184 ms

menu-back.png

menu-back.png

184 ms

banner_2b.jpg

banner_2b.jpg

273 ms

love-and-desire-woman-100.jpg

love-and-desire-woman-100.jpg

288 ms

love-and-desire-woman-100-gold.jpg

love-and-desire-woman-100-gold.jpg

293 ms

love-and-desire-man-100-gold.jpg

love-and-desire-man-100-gold.jpg

298 ms

love-and-desire-man-100.jpg

love-and-desire-man-100.jpg

286 ms

manestys_woman.jpg

manestys_woman.jpg

273 ms

no_picture.gif

no_picture.gif

378 ms

header_bg.png

header_bg.png

359 ms

best.png

best.png

388 ms

home.woff

home.woff

400 ms

sdk.js

sdk.js

145 ms

footer-phero-de.png

footer-phero-de.png

404 ms

168 ms

ajax-loader.gif

ajax-loader.gif

260 ms

collect

collect

44 ms

sdk.js

sdk.js

6 ms

collect

collect

42 ms

41 ms

38 ms

ga-audiences

ga-audiences

15 ms

banner_2.jpg

banner_2.jpg

307 ms

Accessibility Review

pheromone.de accessibility score

52

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.

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

pheromone.de best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pheromone.de SEO score

63

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

Document doesn't have a <title> element

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Pheromone.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 Pheromone.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

pheromone.de

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