Trailing letter redirect

Sorry for the late reply. Why is there a link with a trailing letter to start with? I can explain how your example link gets redirected to /furniture-faux/hand-made-furniture/ though. When WP cannot find an exact match to the request, WP then interprets your request as “get any post/page that begins with ‘h'”. The hand-made-furniture page was the first one found starting with “h”, so that is what was served. The fact it belongs to a different hierarchical branch is disregarded, it’s a page whose slug begins with “h”.

How do I fix this? It’s killing my page load speed and there is nothing wrong with the link and/or the slug on either page. It’s also showing up on every page when I look at the “network” tab in the developer tools. I would attach a screenshot but I dont see an option

These forums don’t support image uploads. You can upload to an image hosting service like imgur.com and leave the link here. For screenshots it’s easier to use snipboard.io. Except you cannot edit the image first, so be careful with what tabs you have up ??

That said, I’ve seen the redirect for myself. Are you saying /mural-projects/faux-fresco-project-1/h is a legitimate link that is wrongly redirected elsewhere? Redirecting “h” is normal behavior when there is no matching page slug. Whats strange is a second request to the same page that was actually served, hand-made-furniture in this case. My network tool says the initiator is an image. I’ve not encountered this before and don’t even know how it’s possible.

The /mural-projects/faux-fresco-project-1/ is a blog post that does not need to be redirected. The /h is what’s redirecting it unnecessarily and this same 301 exists on every post and page. Look at a few more posts and pages instead of just one with the dev tools and you will find that it’s killing my load time and needs to be fixed somehow.

What brought my attention to it was Lighthouse and GTMatrix “opportunities” It gave me a bad rating for “minimize redirects” and pointing to links with the trailing /h

Redirecting “/h” is normal behavior when WP cannot find a post matching that request. The question to you is why is there “/h” in the link to begin with? If you want /faux-fresco-project-1 post, that should be what is requested, without any “/h”. If you don’t know the answer, we can try and find out. The link is the problem, not the redirect.

I did not create that link. For some reason, it created itself as both those posts have always been independent of one another. This is also not the only instance that this has happened. My question is why as a 301 redirect is it delaying my load speed. If you look you will see that that’s the case, I mean if there is no redirect then why is it loading in the first place. I am no developer I am just looking for reasoning because it doesn’t make sense. If that’s normal for WP then how does anyone get 100% for optimization?

I just check that link again and the /h is at 165B and took 1.82 seconds to load and it was not even redirected. Take a look…https://art-faux2.com/mural-projects/faux-fresco-project-1/

One more thing, How come the /h is not showing in the network on any of my other sites?

rosboundy.com.au
artist-sites.com
creatives-daily.com

Here’s a mobile test report
https://snipboard.io/LFzT1X.jpg

Redirects impact load times because an extra HTTP request needs to be made (requests to WP itself are particularly time consuming). That’s not good, but even worse is users are not being served the page they wanted. The extra /h does not belong there, there’s something amiss with that site. Your other sites are apparently fine and working as they should. If we can eliminate unwanted link elements, it’ll improve your page speed.

The links WP generates are filterable so that your theme or plugins can alter the final form of the link. That’s useful when things work as they should. When something isn’t coded correctly it can cause strange behavior like this.

Before we try to narrow down the source of the issue, please visit the permalinks settings admin screen. This causes WP to regenerate its rewrite rules. It’s possible the errant code has been fixed and the related rewrite rules are stale.

If links still have the /h or similar, temporarily switch to twentytwenty theme and deactivate all plugins. Visit the permalinks screen again. Links should now be correct, without trailing /h. Restore your theme, then plugins, one at a time. Revisit the permalinks screen after each, then check links again. When the trailing /h reappears, the last activated module is the cause.

My theme is generate press,

I am experiencing the effects firsthand and I have done the general troubleshooting as you have directed and there is no change. You refer to the “Permalinks screen” and I am very familiar with the admin screen, but how do you view the links? Is there suppose to be a list of links? If so I have never seen one…unless you are speaking of viewing the links from the network screen

• This reply was modified 4 years, 3 months ago by art137.

There are no links to view, the rewrite rules are managed by WP internally, they are not visible through the normal UI. It’s just that visiting that one screen triggers an internal regeneration of the rules, which is necessary when permalink related code has changed. Plugins and themes can also trigger it themselves by calling flush_rewrite_rules().

Ruling out plugins or theme is good. That leaves us with few other possibilities. Open the faux-fresco-project-1 page/post for editing and check there if its permalink slug there has the /h or not. If it does, remove it and update the page.

Do you have a /wp-content/mu-plugins/ folder which has any files in it? Anything there could be a cause. Try temporarily renaming the folder, then revisiting the permalinks screen.

Check your .htaccess file for any rules that could be adding the /h.

This makes the second time I have tried to respond. I don’t know why it was gone when I came back but my response was not here so I will post again.

I checked the mu-plugins folder and found the GoDaddy worker plugin and deactivated it and nothing had changed

I checked the Fresco-1 post and there was no /h in the slug

There is no /h in the slug or anywhere else and this is effecting nearly every post on my site

This time it popped up on this post I am trying to optimize. The /h shows 942.4ms and the same page of /hand-made-furniture/ is at 1.95s

Here is the link to the post it is showing in
https://art-faux2.com/marbling-techniques/another-faux-marble-on-columns/

I checked the .htaccess file and I see nothing referring to the /h

• This reply was modified 4 years, 3 months ago by art137.

I tried to see if it could possibly be something with the hand-made-furniture/ post so I disabled it and put it into the draft.

the ‘h’ was still present and it redirected to a different post.

When I republished the post, it redirected back to the /hand-made-furniture/ post again

This issue between both the /h and redirect is adding on average of 3 to 5 secs on my page load depending on how large the post is. It pops up on any post I run a speed test on and even in the dev tools

I also ran a test on the post itself and the /h chimed in at 1.09s and it redirected to itself at 9.3ms

• This reply was modified 4 years, 3 months ago by art137.
• This reply was modified 4 years, 3 months ago by art137.

The only other cause I can think of is that some core file was modified, adding code that does this. Try doing a manual “update”, except use a fresh download of your current version as the source.

I read the instructions and I’m not sure if I can do this without screwing it up and losing everything.
There is this line that confuses me;

For these instructions, it is assumed that your blog’s URL is https://example.com/wordpress/.

This is not affecting just my blog, it’s the whole website including pages. With the /hand-painted-furniture/ post de-activated (draft) it just picks another post.
I don’t know how anything could have been added to the core files as I am the only one who has had access to the root files

If this ‘manual update’ does not fix it what is the next step and/or is there one?
There has to be a way to find the cause of this without taking a chance like this.

Also I have upgraded to 5.5 already through the WP update

• This reply was modified 4 years, 3 months ago by art137.
• This reply was modified 4 years, 3 months ago by art137.