Holzlaborbern.Ch - Info holzlaborbern.ch

holzlaborbern.ch receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank holzlaborbern.ch is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Switzerland and links to network IP address 193.138.214.42. This server supports HTTPS and HTTP/2.

About - holzlaborbern.ch


holzlaborbern.ch Profile

Description: Die etwas andere Schreinerei in der Lorraine in Bern
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with holzlaborbern.ch in any way. Only publicly available statistics data are displayed.

How popular is holzlaborbern.ch?

Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  holzlaborbern.ch
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

How socially engaged is holzlaborbern.ch?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
holzlaborbern.ch
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report

Root domain:
holzlaborbern.ch
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

How much holzlaborbern.ch can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do holzlaborbern.ch lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is holzlaborbern.ch worth?

Website Value:
n/a

Where is holzlaborbern.ch hosted?

Server IP:
193.138.214.42
ASN:
AS15576 
ISP:
NTS workspace AG 
Server Location:

Switzerland, CH
 

Other sites hosted on 193.138.214.42

There are no other sites hosted on this IP

How fast does holzlaborbern.ch load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
90 ms
Other
26 ms
Style & Layout
12 ms
Script Parsing & Compilation
7 ms
Parse HTML & CSS
6 ms
Rendering
3 ms
Serve images in next-gen formats - Potential savings of 34 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
168 KB34 KB
Avoids an excessive DOM size - 77 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
77
Maximum DOM Depth
9
Maximum Child Elements
8
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://holzlaborbern.ch/)
0
https://holzlaborbern.ch/
190
Keep request counts low and transfer sizes small - 13 requests • 279 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
13279 KB
Image
3174 KB
Script
567 KB
Font
230 KB
Document
14 KB
Stylesheet
13 KB
Other
10 KB
Media
00 KB
Third-party
223 KB
Eliminate render-blocking resources - Potential savings of 210 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
3 KB70
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
34 KB190
https://holzlaborbern.ch/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4 KB150
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://holzlaborbern.ch/
0 ms111 ms0 KB0 KB301text/html
https://holzlaborbern.ch/
111 ms223 ms4 KB9 KB200text/htmlDocument
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
233 ms349 ms3 KB11 KB200text/cssStylesheet
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
233 ms459 ms34 KB95 KB200application/javascriptScript
https://holzlaborbern.ch/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
234 ms460 ms4 KB10 KB200application/javascriptScript
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
234 ms669 ms168 KB168 KB200image/jpegImage
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png
235 ms670 ms5 KB5 KB200image/pngImage
https://holzlaborbern.ch/wp-content/plugins/simple-colorbox/scripts/jquery.colorbox-min.js?ver=1
493 ms670 ms5 KB12 KB200application/javascriptScript
https://holzlaborbern.ch/wp-includes/js/wp-embed.min.js?ver=4.7.5
494 ms671 ms1 KB1 KB200application/javascriptScript
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
496 ms720 ms27 KB27 KB200application/font-woffFont
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
496 ms721 ms3 KB2 KB200application/font-woffFont
https://matomo.momou.ch/js/index.php
503 ms737 ms23 KB66 KB200application/javascriptScript
https://matomo.momou.ch/js/index.php?action_name=Schreinerei%20Holzlabor%20Bern%20%7C%20Die%20etwas%20andere%20Schreinerei%20in%20der%20Lorraine%20in%20Bern&idsite=4&rec=1&r=077482&h=3&m=16&s=38&url=https%3A%2F%2Fholzlaborbern.ch%2F&_id=4f90cc8b22e5511a&_idts=1562926599&_idvc=1&_idn=0&_refts=0&_viewts=1562926599&send_image=1&cookie=1&res=800x600>_ms=113&pv_id=c1xcqd
759 ms890 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
0 ms168 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
0 ms27 KB
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png
0 ms5 KB
https://holzlaborbern.ch/wp-content/plugins/simple-colorbox/scripts/jquery.colorbox-min.js?ver=1
0 ms5 KB
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
0 ms3 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
0 ms3 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
242 ms
6 ms
368 ms
38 ms
483 ms
22 ms
505 ms
6 ms
511 ms
8 ms
692 ms
14 ms
757 ms
19 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
224 ms
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
225 ms
Remove unused CSS - Potential savings of 3 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
3 KB3 KB
Avoids enormous network payloads - Total size was 279 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
168 KB
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
34 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
27 KB
https://matomo.momou.ch/js/index.php
23 KB
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png
5 KB
https://holzlaborbern.ch/wp-content/plugins/simple-colorbox/scripts/jquery.colorbox-min.js?ver=1
5 KB
https://holzlaborbern.ch/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4 KB
https://holzlaborbern.ch/
4 KB
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
3 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
3 KB
Minimize Critical Requests Depth - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 110 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Contentful Paint (3G) 3450 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 3.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
515 ms
8 ms
651 ms
41 ms
764 ms
21 ms
786 ms
6 ms
792 ms
11 ms
1308 ms
19 ms
1444 ms
22 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
506 ms
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
506 ms
JavaScript execution time - 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
204 ms15 ms4 ms
https://holzlaborbern.ch/
166 ms162 ms4 ms
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
152 ms120 ms8 ms
https://matomo.momou.ch/js/index.php
88 ms82 ms6 ms
Remove unused CSS - Potential savings of 3 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
3 KB3 KB
Avoids enormous network payloads - Total size was 279 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
168 KB
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
34 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
27 KB
https://matomo.momou.ch/js/index.php
23 KB
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png
5 KB
https://holzlaborbern.ch/wp-content/plugins/simple-colorbox/scripts/jquery.colorbox-min.js?ver=1
5 KB
https://holzlaborbern.ch/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4 KB
https://holzlaborbern.ch/
4 KB
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
3 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
3 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
396 ms
Other
110 ms
Style & Layout
57 ms
Script Parsing & Compilation
30 ms
Parse HTML & CSS
28 ms
Rendering
11 ms
Garbage Collection
4 ms
Serve images in next-gen formats - Potential savings of 34 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
168 KB34 KB
Avoids an excessive DOM size - 77 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
77
Maximum DOM Depth
9
Maximum Child Elements
8
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://holzlaborbern.ch/)
0
https://holzlaborbern.ch/
630
Keep request counts low and transfer sizes small - 13 requests • 279 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
13279 KB
Image
3174 KB
Script
567 KB
Font
230 KB
Document
14 KB
Stylesheet
13 KB
Other
10 KB
Media
00 KB
Third-party
223 KB
Eliminate render-blocking resources - Potential savings of 530 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
3 KB180
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
34 KB330
https://holzlaborbern.ch/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
4 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://holzlaborbern.ch/
0 ms256 ms0 KB0 KB301text/html
https://holzlaborbern.ch/
256 ms486 ms4 KB9 KB200text/htmlDocument
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
500 ms622 ms3 KB11 KB200text/cssStylesheet
https://holzlaborbern.ch/wp-includes/js/jquery/jquery.js?ver=1.12.4
500 ms731 ms34 KB95 KB200application/javascriptScript
https://holzlaborbern.ch/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
500 ms731 ms4 KB10 KB200application/javascriptScript
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
501 ms1271 ms168 KB168 KB200image/jpegImage
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png
501 ms1271 ms5 KB5 KB200image/pngImage
https://holzlaborbern.ch/wp-content/plugins/simple-colorbox/scripts/jquery.colorbox-min.js?ver=1
764 ms1272 ms5 KB12 KB200application/javascriptScript
https://holzlaborbern.ch/wp-includes/js/wp-embed.min.js?ver=4.7.5
764 ms1272 ms1 KB1 KB200application/javascriptScript
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
766 ms1272 ms27 KB27 KB200application/font-woffFont
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
766 ms1273 ms3 KB2 KB200application/font-woffFont
https://matomo.momou.ch/js/index.php
777 ms1412 ms23 KB66 KB200application/javascriptScript
https://matomo.momou.ch/js/index.php?action_name=Schreinerei%20Holzlabor%20Bern%20%7C%20Die%20etwas%20andere%20Schreinerei%20in%20der%20Lorraine%20in%20Bern&idsite=4&rec=1&r=077482&h=3&m=16&s=33&url=https%3A%2F%2Fholzlaborbern.ch%2F&_id=119545df18e50542&_idts=1562926593&_idvc=1&_idn=0&_refts=0&_viewts=1562926593&send_image=1&cookie=1&res=412x660>_ms=230&pv_id=c1xcqd
1440 ms1625 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg
0 ms168 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff
0 ms27 KB
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png
0 ms5 KB
https://holzlaborbern.ch/wp-content/plugins/simple-colorbox/scripts/jquery.colorbox-min.js?ver=1
0 ms5 KB
https://holzlaborbern.ch/wp-content/themes/houzi/style.css
0 ms3 KB
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff
0 ms3 KB
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 230 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Size 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 <a href="https://holzlaborbern.ch/">HOLZLABOR</a> is close to 1 other tap targets .
The tap target <a href="https://holzla…n.ch/uber-uns/">Über uns</a> and 11 others are close to other tap targets .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

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

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

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://holzlaborbern.ch/wp-content/themes/houzi/style.css

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Valerie Gosteli and 11 others render only 7 pixels tall (18 CSS pixels) .

Leverage 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://holzlaborbern.ch/wp-content/themes/houzi/fonts/akzigbem-webfont.woff (expiration not specified)
https://holzlaborbern.ch/wp-content/themes/houzi/fonts/holzlabor.woff (expiration not specified)
https://holzlaborbern.ch/wp-content/themes/houzi/images/logo.png (expiration not specified)
https://holzlaborbern.ch/wp-content/themes/houzi/style.css (expiration not specified)
https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg (expiration not specified)

Optimize images

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

Optimize the following images to reduce their size by 32.1KiB (20% reduction).

Compressing https://holzlaborbern.ch/wp-content/uploads/2012/09/schreinerei-holzlabor-bern.jpg could save 32.1KiB (20% reduction).

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 993 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <h2>Schreinerei Holzlabor</h2> falls outside the viewport.
The element <p></p> falls outside the viewport.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 377B (15% reduction).

Minifying https://holzlaborbern.ch/wp-content/themes/houzi/style.css could save 377B (15% reduction) after compression.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

Does holzlaborbern.ch use compression?

holzlaborbern.ch use gzip compression.
Original size: 8.95 KB
Compressed size: 3.17 KB
File reduced by: 5.78 KB (64%)

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

SSL Checker - SSL Certificate Verify

holzlaborbern.ch supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: holzlaborbern.ch
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Jul 2 16:27:44 2019 GMT
Valid until: Sep 30 16:27:44 2019 GMT
Authority:
Keysize:

Verify HTTP/2 Support

holzlaborbern.ch supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

Http Header

Server: nginx
Date: Fri, 12 Jul 2019 10:16:19 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: https://holzlaborbern.ch/

HTTP/2 200 
server: nginx
date: Fri, 12 Jul 2019 10:16:19 GMT
content-type: text/html; charset=UTF-8
set-cookie: PHPSESSID=tskagfb58vo8f71pbiegehiah0; path=/; HttpOnly
x-pingback: https://holzlaborbern.ch/xmlrpc.php
link: <https://holzlaborbern.ch/wp-json/>; rel="https://api.w.org/"
link: <https://holzlaborbern.ch/>; rel=shortlink
content-encoding: gzip
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
x-permitted-cross-domain-policies: none
x-download-option: noopen

DNS Lookup

Type Ip Target TTL
AAAA 3600
TXT 3600
MX mail.momou.ch 3600
SOA 3600
Mname ns1.gandi.net
Rname hostmaster.gandi.net
Serial Number 1562803200
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 193.138.214.42 3600
NS ns-48-b.gandi.net 3592
NS ns-244-c.gandi.net 3592
NS ns-6-a.gandi.net 3592

Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.nic.ch...
Requests of this client are not permitted. Please use https://www.nic.ch/whois/ for queries.
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with holzlaborbern.ch in any way. Only publicly available statistics data are displayed.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
holzlaborbern.ch widget