Search pages can show up as results for search pages.
Actually, the search is pretty terrible in general. Try searching for "ranks". You end up finding a search for all posts by PT_, but not the topic I was looking for ("Ranks? how to get them and how much to the next rank"). I literally had to copy the exact name into the search bar before I found it. Also, the search shows 4 pages, but 3 and 4 show a "no results" page.

Search isn't ran via phpBB anymore, it's done through Google. Which is why it's the only part of the site with ads. So, you'd have better luck asking Google. :/

Adding to that; I think that making the site actually user friendly would be nice When I click on 'Forum' there's just a huge page that has literally nothing I'm looking for if I have a simple question; which rather off putting. There is no way to just make a topic and assign it a tag; like how stack overflow does. Not by forcing users to assign tags; but rather creating a database which classifies topics under tags. Then admins can add tags if users require it. This creates a much better indexing system and finding topics hundreds of times easier than hoping the search bar can actually find what I am looking for.

It happens to me too. It might be Chrome, it never happens to me when I use Safari, though.

When you view a webpage, "pings" are sent occasionally to make sure that the connection doesn't quit, IIRC.

This issue has been reported so many times. It's not a browser bug and definitely server side. We can't track it down but suspect it has to do with how phpBB handles topics with hundreds of replies. At the time of Womp Womps post, this topic had 820 replies. Or, 41 pages of replies. However, phpBB doesn't include the OP in the reply count. So there was really 821 posts which would have pushed us into 42 pages. However, the correct last post is on page 41

So, somewhere along the lines phpBB is counting the correct number of pages for the amount of posts but then erring out that there are no posts for the same topic. Which is why we suspect it's a high reply count thing. It also doesn't happen every time there's a new page which makes it pretty hard to track down and a fairly low priority; if it happened with every new page we'd probably spend more of our free time tracking it down.

Or don't force a dependency on some other service and escape the characters it doesn't like.

This works.

Code:

... in Edge.