Long waiting (TTFB) times for all requests (multiple seconds) from custom domain (.de)

Hello,

my site is very pooly when trying to access it from my custom domain, which is a german domain rented from IONOS 1&1.

Any ideas what could be causing the issues? I posted the waterfall diagram below.

site: https://relaxed-ritchie-c1284b.netlify.app/
custom domain: https://marquetry.de/

Hey there, @Permalink-stone-suit :wave:

Welcome to the Netlify Forums :netliconfetti:

Are you by chance proxying to Netlify? I want to rule that out first as we do not recommend proxying to us .

My second question: does your site contain large images? If it does, this could cause longer load times.

Let us know!

Hi hillary,

and thank you for the fast reply. I have not setup up any proxy between the netlify site and my domain. I directly edited the A record in my IONOS control panel to redirect my domain to my netlify site.

The problem is that everything suddenly becomes very slow. Especially the wait times. For example, there is a 2 second wait, before the first file, the index.js file (which contains my html) is loaded. After 2 seconds, all other files will be loaded, and they all are pretty slow. In download speed and waiting time.

This is the same site accesed through IONOS web hosting: https://kunstschreinerei-matt.de/. It is nearly instantaneous, as you can see in this waterfall graph:

hi @Permalink-stone-suit - would you please capture a HAR file for us so we can take a closer look?

https://toolbox.googleapps.com/apps/har_analyzer/

I wonder if this is a local issue, because I’m not seeing this from where I am in Arizona.

|======================== check load time =======================
| ------------------------ marquetry.de ------------------------
This is ApacheBench, Version 2.3 <$Revision: 1879490 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking marquetry.de (be patient).....done


Server Software:        Netlify
Server Hostname:        marquetry.de
Server Port:            80

Document Path:          /
Document Length:        36 bytes

Concurrency Level:      1
Time taken for tests:   0.073 seconds
Complete requests:      1
Failed requests:        0
Non-2xx responses:      1
Total transferred:      317 bytes
HTML transferred:       36 bytes
Requests per second:    13.79 [#/sec] (mean)
Time per request:       72.514 [ms] (mean)
Time per request:       72.514 [ms] (mean, across all concurrent requests)
Transfer rate:          4.27 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:       35   35   0.0     35      35
Processing:    38   38   0.0     38      38
Waiting:       38   38   0.0     38      38
Total:         72   72   0.0     72      72

| ---------------------- www.marquetry.de ----------------------
This is ApacheBench, Version 2.3 <$Revision: 1879490 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.marquetry.de (be patient).....done


Server Software:        Netlify
Server Hostname:        www.marquetry.de
Server Port:            80

Document Path:          /
Document Length:        40 bytes

Concurrency Level:      1
Time taken for tests:   0.069 seconds
Complete requests:      1
Failed requests:        0
Non-2xx responses:      1
Total transferred:      325 bytes
HTML transferred:       40 bytes
Requests per second:    14.45 [#/sec] (mean)
Time per request:       69.218 [ms] (mean)
Time per request:       69.218 [ms] (mean, across all concurrent requests)
Transfer rate:          4.59 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:       34   34   0.0     34      34
Processing:    35   35   0.0     35      35
Waiting:       35   35   0.0     35      35
Total:         69   69   0.0     69      69
|================================================================

Sorry for not answering for so long.

I noticed that the problem had suddenly gone away, after 1/2 days of waiting. Maybe this is a problem with the DNS server which is used be german ISPs, because after switching to Netlify DNS, the site was not reachable for some time, but it was reachable when using the google DNS for example.

Now it seems like everything is working fine! Thank you for your fast help perry, hillary and gregraven!