this was your old site blog.johnnyreilly.com (note:hosted on on the blog subdomain) https://www.google.com/search?q=site%3Ablog.johnnyreilly.com... https://web.archive.org/web/20230000000000*/https://blog.joh... archive.org picks it up until december 2022
this is your current site https://johnnyreilly.com/ (note: no subdomain() https://www.google.com/search?q=site%3Ajohnnyreilly.com&pws=... archive.org seems to pic it up late december 2022, start 2023 https://web.archive.org/web/20230000000000*/https://johnnyre...
between old pages and new pages you have a redirect chain https://blog.johnnyreilly.com/page/201/ -> 301 -> https://johnnyreilly.com/page/201/ -> https://johnnyreilly.com/page/201 final destination (which does not seem to be the correct new URL)
you had an domain movie, URL change and a subideal old 2 new migration if you do not want to loose traffic with URL changes, follwo this spec to the letter https://developers.google.com/search/docs/crawling-indexing/...
if you do not do this correctly a traffic pattern like yours must be expected.
if you do this now you might be abble to recup about 50% of your old traffic, might
additionally you haver massive self made internal duplicate content (tag pages show full pages), soft 404 (non existing pages i.e.: https://johnnyreilly.com/page/fake-url-for-soft-404-error-ch... trigger HTTP 302 redirects and then even more behaviour)