PREFA.DE PREFA Deutschland | PREFA

prefa.de Website Information

Daily Unique Visits: 2,341

Daily Page Views: 7,023

Income Per Day: $21

Estimated Value: $7,560

This website is located in Germany and is using following IP address 62.113.230.93. See the complete list of popular websites hosted in Germany.

prefa.de is registered under .DE top-level domain. Please check other sites in .DE zone.

Website prefa.de is using the following name servers:

  • ns21.netronics.at
  • ns23.netronics.at
  • ns22.netronics.at

and is probably hosted by 23media GmbH. See the full list of other websites hosted by 23media GmbH.

The highest website prefa.de position in Alexa rank database was 21735 and the lowest rank position was 998494. Current position of prefa.de in Alexa rank database is 459429.

Desktop speed score of prefa.de (71/100) is better than the results of 52.66% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of prefa.de (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of prefa.de (55/100) is better than the results of 43.86% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

prefa.de Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


prefa.de whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain: prefa.de
Status: connect

prefa.de server information

Servers Location

prefa.de desktop page speed rank

Last tested: 2019-11-30


Desktop Speed Medium
71/100

prefa.de Desktop Speed Test Quick Summary


priority - 14Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 139.7KiB (32% reduction).

Compressing https://www.prefa.de/fileadmin/_processed_/c/9/csm…efalz-H_5d1daf2559.jpg could save 34.3KiB (30% reduction).
Compressing https://www.prefa.de/fileadmin/user_upload/Content…utz-Content-Teaser.jpg could save 28.8KiB (37% reduction).
Compressing https://www.prefa.de/fileadmin/_processed_/e/5/csm…ader-DE_7008e9327b.jpg could save 25.9KiB (43% reduction).
Compressing https://www.prefa.de/fileadmin/user_upload/Content…ge-kostenlos-small.jpg could save 18.4KiB (39% reduction).
Compressing https://www.prefa.de/fileadmin/user_upload/Content…and-Wasungen-gross.jpg could save 18KiB (23% reduction).
Compressing https://www.prefa.de/fileadmin/user_upload/Content…e-bestellen-Teaser.jpg could save 14.2KiB (24% reduction).

priority - 12Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.prefa.de/typo3temp/compressor/merged-e…6bb3e1ec.js?1509618570
https://www.prefa.de/typo3temp/compressor/merged-0…4ea63d59.js?1537275170
https://www.prefa.de/typo3temp/compressor/merged-1…4e37a8cd.js?1574071004
https://www.prefa.de/typo3temp/compressor/merged-d…b5577cc8.js?1572960351

Optimize CSS Delivery of the following:

https://www.prefa.de/typo3temp/compressor/merged-1…d7f874c.css?1573819083

priority - 7Reduce server response time

In our test, your server responded in 0.72 seconds.

priority - 2Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 23.2KiB (18% reduction).

Minifying https://www.prefa.de/typo3temp/compressor/merged-1…4e37a8cd.js?1574071004 could save 16.7KiB (15% reduction) after compression.
Minifying https://www.prefa.de/typo3temp/compressor/merged-d…b5577cc8.js?1572960351 could save 6.5KiB (38% reduction) after compression.

priority - 2Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.googletagmanager.com/gtm.js?id=GTM-K2B47XK (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/142008…4524?v=2.9.14&r=stable (20 minutes)
https://s.pinimg.com/ct/core.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://sjs.bizographics.com/insight.min.js (10.1 hours)

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 12% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

prefa.de Desktop Resource Breakdown

Total Resources50
Number of Hosts14
Static Resources32
JavaScript Resources11
CSS Resources1

prefa.de mobile page speed rank

Last tested: 2017-05-19


Mobile Speed Bad
55/100

prefa.de Mobile Speed Test Quick Summary


priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.prefa.de/typo3temp/compressor/merged-ea…34b6741a.js?1447941889
http://www.prefa.de/typo3temp/compressor/merged-89…ba369f9d.js?1470398106
http://www.prefa.de/typo3temp/compressor/merged-78…b5f1aa6d.js?1495198220
http://www.prefa.de/typo3temp/compressor/merged-4c…efb1a9c4.js?1451482071

Optimize CSS Delivery of the following:

http://www.prefa.de/typo3temp/compressor/merged-96…d242877.css?1495095210

priority - 38Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 367.9KiB (31% reduction).

Compressing http://www.prefa.de/fileadmin/_processed_/a/0/csm_…nnspiel_b18180f635.jpg could save 100KiB (26% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/f/b/csm_…600x800_ff6a8e5022.jpg could save 58.7KiB (34% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/d/d/csm_…1_small_5f985d6ddc.jpg could save 33.5KiB (36% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/d/e/csm_…4_small_6ebe60b1bb.jpg could save 33.3KiB (35% reduction).
Compressing http://www.prefa.de/fileadmin/user_upload/PREFA_Ko…e_bestellen_Teaser.jpg could save 31.6KiB (65% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/3/0/csm_…2_small_1dfbb6efc2.jpg could save 30.9KiB (35% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/csm_2.Sp…galerie_b491a78bd8.jpg could save 24.6KiB (32% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/b/e/csm_…3_small_f26f7f32dd.jpg could save 17KiB (32% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/csm_2.Sp…service_a9bc250b22.jpg could save 14.3KiB (31% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/csm_1sp_…ersuche_cf17273d61.jpg could save 11.5KiB (31% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/e/d/csm_…600x500_8e98c45637.jpg could save 7KiB (18% reduction).
Compressing http://www.prefa.de/fileadmin/_processed_/d/f/csm_…nsystem_893e8abdf1.png could save 5.5KiB (14% reduction).

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 2% of the final above-the-fold content could be rendered with the full HTML response.

priority - 2Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 14.9KiB (14% reduction).

Minifying http://www.prefa.de/typo3temp/compressor/merged-78…b5f1aa6d.js?1495198220 could save 14.3KiB (14% reduction) after compression.
Minifying https://connect.facebook.net/signals/config/1420082921624524?v=2.7.10 could save 633B (79% reduction) after compression.

priority - 1Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://connect.facebook.net/signals/config/1420082921624524?v=2.7.10 (20 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 1Reduce server response time

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 4.1KiB (31% reduction).

Minifying http://www.prefa.de/ could save 4.1KiB (31% reduction) after compression.

prefa.de Mobile Resource Breakdown

Total Resources39
Number of Hosts7
Static Resources32
JavaScript Resources7
CSS Resources1

prefa.de mobile page usability

Last tested: 2017-05-19


Mobile Usability Good
99/100

prefa.de Mobile Usability Test Quick Summary


priority - 0Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <div id="slider-129052" class="slider owl-car…oaded owl-drag"></div> and 3 others are close to other tap targets.

prefa.de HTML validation

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 22 Column: 1 - 126
"...PO3 CMS"> <meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no"> <meta..."

Errors

Bad start tag in “img” in “head”.

Line: 111 Column: 11 - 137
"...<noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1420082921624524&ev=PageView&noscript=1"/></noscri..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 111 Column: 11 - 137
"...<noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1420082921624524&ev=PageView&noscript=1"/></noscri..."

Stray end tag “noscript”.

Line: 111 Column: - 148
"......"

Stray end tag “head”.

Line: 129 Column: 1 - 7
"... --> </head> <body..."

Start tag “body” seen but an element of the same type was already open.

Line: 130 Column: 1 - 6
"... </head> <body> ..."

prefa.de similar domains

Similar domains:
www.prefa.com
www.prefa.net
www.prefa.org
www.prefa.info
www.prefa.biz
www.prefa.us
www.prefa.mobi
www.refa.de
www.prefa.de
www.orefa.de
www.porefa.de
www.oprefa.de
www.lrefa.de
www.plrefa.de
www.lprefa.de
www.pefa.de
www.peefa.de
www.preefa.de
www.perefa.de
www.pdefa.de
www.prdefa.de
www.pdrefa.de
www.pfefa.de
www.prfefa.de
www.pfrefa.de
www.ptefa.de
www.prtefa.de
www.ptrefa.de
www.prfa.de
www.prwfa.de
www.prewfa.de
www.prwefa.de
www.prsfa.de
www.presfa.de
www.prsefa.de
www.prdfa.de
www.predfa.de
www.prrfa.de
www.prerfa.de
www.prrefa.de
www.prea.de
www.preca.de
www.prefca.de
www.precfa.de
www.preda.de
www.prefda.de
www.prera.de
www.prefra.de
www.preta.de
www.prefta.de
www.pretfa.de
www.prega.de
www.prefga.de
www.pregfa.de
www.preva.de
www.prefva.de
www.prevfa.de
www.pref.de
www.prefq.de
www.prefaq.de
www.prefqa.de
www.prefw.de
www.prefaw.de
www.prefwa.de
www.prefs.de
www.prefas.de
www.prefsa.de
www.prefz.de
www.prefaz.de
www.prefza.de

prefa.de Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


prefa.de TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.