FrogFind would not load the information on my home page. However, other pages, such as the articles that I have written, would load. This was likely due to FrogFind using Mozilla's Readability library to find the main content of a page.
Wrapping a <main> tag around the index page allowed FrogFind to properly detect the HTML. When I tried the same solution on my contact page, FrogFind was still unable to show its information. The work-around was to wrap it in an <article> tag.
FrogFind Does Not Read Relative Paths Correctly
On modern browsers, if https://riazj.com/articles/fix-frogfind-content-display is opened, any links on that
page to another file like
href="repairing-thinkpads-and-macbooks" will be within the
articles' folder because the current page is in that folder. With FrogFind, it will instead search from the root domain
(https://riazj.com). This means that if one article links to another without stating the absolute path
(/articles/article-name), FrogFind will look at https://riazj.com/article-name.
The solutions that I have found are to add a <base> tag in the <head> tag of the affected pages, or to type out the full path. Since the number of people visiting this site through FrogFind besides me is likely zero, I have decided to not change the articles' links.