feneberg.de Website Information
Daily Unique Visits: 734
Daily Page Views: 1,468
Income Per Day: $5
Estimated Value: $1,200
feneberg.de is registered under .DE top-level domain. Please check other sites in .DE zone.
No name server records were found.
and is probably hosted by Bradler & Krantz GmbH & Co. KG. See the full list of other websites hosted by Bradler & Krantz GmbH & Co. KG.
The highest website feneberg.de position in Alexa rank database was 85428 and the lowest rank position was 997037. Current position of feneberg.de in Alexa rank database is 977240.
Desktop speed score of feneberg.de (78/100) shows that the page desktop performance can be improved.
Mobile usability score of feneberg.de (94/100) means that the page is mobile-friendly.
Mobile speed score of feneberg.de (52/100) shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
feneberg.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.
feneberg.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.
Status: connect
feneberg.de server information
Servers Location
feneberg.de desktop page speed rank
Last tested: 2017-02-06
feneberg.de Desktop Speed Test Quick Summary
priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 14 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.feneberg.de/fileadmin/templates_fenebe…/wow.min.js?1446556232
https://www.feneberg.de/typo3temp/javascript_dd82474708.js?1426866291
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
https://www.feneberg.de/fileadmin/templates_feneberg/js/slick/slick.min.js
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…owbox/shadowbox.mod.js
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…s/shadowbox/lang/de.js
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…themes/default/skin.js
https://www.feneberg.de/typo3conf/ext/mp_jquery/Re…external/matchmedia.js
https://www.feneberg.de/typo3conf/ext/mp_jquery/Re…ill/picturefill.mod.js
https://www.feneberg.de/fileadmin/templates_fenebe…y.cookie.js?1416835352
https://www.feneberg.de/fileadmin/templates_fenebe…kieFuncs.js?1463994087
https://www.feneberg.de/fileadmin/templates_fenebe…trap.min.js?1423130294
https://www.feneberg.de/fileadmin/templates_fenebe…feneberg.js?1428416977
Optimize CSS Delivery of the following:
https://www.feneberg.de/typo3conf/ext/sr_language_…ageMenu.css?1453315075
https://www.feneberg.de/fileadmin/templates_fenebe…otstrap.css?1481553854
https://fonts.googleapis.com/css?family=Signika:300,600&subset=latin
https://www.feneberg.de/fileadmin/templates_fenebe…ss/base.css?1485354353
https://www.feneberg.de/fileadmin/templates_fenebe…ate.min.css?1447239421
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…hemes/default/skin.css
https://www.feneberg.de/typo3conf/ext/mp_dynamiche…s/mp_dynamicHeader.css
priority - 7Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.feneberg.de/
https://www.feneberg.de/
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.
priority - 1Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 7.5KiB (33% reduction).
Compressing https://www.feneberg.de/fileadmin/templates_fenebe…cons/logo_feneberg.png could save 3.2KiB (22% reduction).
priority - 1Minify 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 4KiB (26% reduction).
Minifying https://www.feneberg.de/fileadmin/templates_feneberg/js/sonic.js?1314341540 could save 573B (28% reduction) after compression.
Minifying https://www.feneberg.de/fileadmin/templates_fenebe…y.cookie.js?1416835352 could save 564B (42% reduction) after compression.
priority - 0Leverage 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:
priority - 0Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2KiB (18% reduction).
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 1.7KiB (17% reduction).
feneberg.de Desktop Resource Breakdown
Total Resources | 76 |
Number of Hosts | 6 |
Static Resources | 70 |
JavaScript Resources | 15 |
CSS Resources | 8 |
feneberg.de mobile page speed rank
Last tested: 2017-02-06
feneberg.de Mobile Speed Test Quick Summary
priority - 64Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 14 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.feneberg.de/fileadmin/templates_fenebe…/wow.min.js?1446556232
https://www.feneberg.de/typo3temp/javascript_dd82474708.js?1426866291
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
https://www.feneberg.de/fileadmin/templates_feneberg/js/slick/slick.min.js
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…owbox/shadowbox.mod.js
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…s/shadowbox/lang/de.js
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…themes/default/skin.js
https://www.feneberg.de/typo3conf/ext/mp_jquery/Re…external/matchmedia.js
https://www.feneberg.de/typo3conf/ext/mp_jquery/Re…ill/picturefill.mod.js
https://www.feneberg.de/fileadmin/templates_fenebe…y.cookie.js?1416835352
https://www.feneberg.de/fileadmin/templates_fenebe…kieFuncs.js?1463994087
https://www.feneberg.de/fileadmin/templates_fenebe…trap.min.js?1423130294
https://www.feneberg.de/fileadmin/templates_fenebe…feneberg.js?1428416977
Optimize CSS Delivery of the following:
https://www.feneberg.de/typo3conf/ext/sr_language_…ageMenu.css?1453315075
https://www.feneberg.de/fileadmin/templates_fenebe…otstrap.css?1481553854
https://fonts.googleapis.com/css?family=Signika:300,600&subset=latin
https://www.feneberg.de/fileadmin/templates_fenebe…ss/base.css?1485354353
https://www.feneberg.de/fileadmin/templates_fenebe…ate.min.css?1447239421
https://www.feneberg.de/typo3conf/ext/mp_jquerylib…hemes/default/skin.css
https://www.feneberg.de/typo3conf/ext/mp_dynamiche…s/mp_dynamicHeader.css
priority - 26Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.feneberg.de/
https://www.feneberg.de/
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.
priority - 1Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 7.5KiB (33% reduction).
Compressing https://www.feneberg.de/fileadmin/templates_fenebe…cons/logo_feneberg.png could save 3.2KiB (22% reduction).
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:
priority - 1Minify 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 4KiB (26% reduction).
Minifying https://www.feneberg.de/fileadmin/templates_feneberg/js/sonic.js?1314341540 could save 573B (28% reduction) after compression.
Minifying https://www.feneberg.de/fileadmin/templates_fenebe…y.cookie.js?1416835352 could save 564B (42% reduction) after compression.
priority - 0Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2KiB (18% reduction).
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 1.7KiB (17% reduction).
feneberg.de Mobile Resource Breakdown
Total Resources | 75 |
Number of Hosts | 6 |
Static Resources | 69 |
JavaScript Resources | 15 |
CSS Resources | 8 |
feneberg.de mobile page usability
Last tested: 2017-02-06
feneberg.de Mobile Usability Test Quick Summary
priority - 5Size 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.
<a href="vonhier-punkte/">Vonhier-Punkteprogramm</a>
and 5 others are close to other tap targets.The tap target
<a href="marken/vonhier/">VonHier</a>
and 22 others are close to other tap targets.feneberg.de HTML validation
Warnings
The “navigation” role is unnecessary for element “nav”.
"...den-xs"> <nav class="navbar navbar-fixed-top" role="navigation"> <di..." Line: 346 Column: 2 - 56
"...ble-xs"> <nav class="navbar navbar-fixed-top" role="navigation"> <di..." Line: 348 Column: 4 - 41
"...s-12"> <nav class="navbar" role="navigation"> <..." Line: 1167 Column: 2 - 49
"...footer"> <nav class="navbar navbarTop" role="navigation"> <di..." Line: 1201 Column: 2 - 52
"... </nav> <nav class="navbar navbarBottom" role="navigation"> <di..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...> </div> <section id="header" class="hidden-xs"> <nav..." Line: 345 Column: 1 - 46
"...ion> <section id="mobileHeader" class="visible-xs"> <nav..." Line: 1166 Column: 1 - 21
"...oter--> <section id="footer"> <nav..."
feneberg.de similar domains
www.feneberg.net
www.feneberg.org
www.feneberg.info
www.feneberg.biz
www.feneberg.us
www.feneberg.mobi
www.eneberg.de
www.feneberg.de
www.ceneberg.de
www.fceneberg.de
www.cfeneberg.de
www.deneberg.de
www.fdeneberg.de
www.dfeneberg.de
www.reneberg.de
www.freneberg.de
www.rfeneberg.de
www.teneberg.de
www.fteneberg.de
www.tfeneberg.de
www.geneberg.de
www.fgeneberg.de
www.gfeneberg.de
www.veneberg.de
www.fveneberg.de
www.vfeneberg.de
www.fneberg.de
www.fwneberg.de
www.fewneberg.de
www.fweneberg.de
www.fsneberg.de
www.fesneberg.de
www.fseneberg.de
www.fdneberg.de
www.fedneberg.de
www.frneberg.de
www.ferneberg.de
www.feeberg.de
www.febeberg.de
www.fenbeberg.de
www.febneberg.de
www.feheberg.de
www.fenheberg.de
www.fehneberg.de
www.fejeberg.de
www.fenjeberg.de
www.fejneberg.de
www.femeberg.de
www.fenmeberg.de
www.femneberg.de
www.fenberg.de
www.fenwberg.de
www.fenewberg.de
www.fenweberg.de
www.fensberg.de
www.fenesberg.de
www.fenseberg.de
www.fendberg.de
www.fenedberg.de
www.fendeberg.de
www.fenrberg.de
www.fenerberg.de
www.fenreberg.de
www.feneerg.de
www.feneverg.de
www.fenebverg.de
www.fenevberg.de
www.fenegerg.de
www.fenebgerg.de
www.fenegberg.de
www.feneherg.de
www.fenebherg.de
www.fenehberg.de
www.fenenerg.de
www.fenebnerg.de
www.fenenberg.de
www.fenebrg.de
www.fenebwrg.de
www.fenebewrg.de
www.fenebwerg.de
www.fenebsrg.de
www.fenebesrg.de
www.fenebserg.de
www.fenebdrg.de
www.fenebedrg.de
www.fenebderg.de
www.fenebrrg.de
www.feneberrg.de
www.fenebrerg.de
www.fenebeg.de
www.fenebeeg.de
www.fenebereg.de
www.fenebeerg.de
www.fenebedg.de
www.feneberdg.de
www.fenebefg.de
www.feneberfg.de
www.fenebefrg.de
www.fenebetg.de
www.fenebertg.de
www.fenebetrg.de
www.feneber.de
www.feneberf.de
www.fenebergf.de
www.feneberv.de
www.fenebergv.de
www.fenebervg.de
www.fenebert.de
www.fenebergt.de
www.feneberb.de
www.fenebergb.de
www.feneberbg.de
www.fenebery.de
www.fenebergy.de
www.feneberyg.de
www.feneberh.de
www.fenebergh.de
www.feneberhg.de
feneberg.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.
feneberg.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.