How to Fix “Remove Following Redirect Chain” Error (4 Methods)
How to Fix “Remove Following Redirect Chain” Error (4 Methods)
GTmetrix: helpful for keeping your site running at top speed ⚡️, confusing when it pulls up the “Remove Following Redirect Chain” error message 😫 Learn how to fix it here ⬆️
👉Subscribe: https://www.youtube.com/c/Kinsta?sub_…
To keep your site in tip-top shape, you need to test it regularly. However, there’s one GTmetrix error message that’s been confusing WordPress website owners: “Remove the following redirect chain if possible.”
If you’re encountering this error, there are ways to figure out what’s causing so many redirects. Once you’ve identified the culprit, stripping out all of those performance-sapping redirects may be as straightforward as pressing a few buttons in your WordPress dashboard.
In this video, we’ll share four ways to resolve the “Remove Following Redirect Chain” error and get your WordPress website back on track.
ℹ️ About Kinsta
Kinsta is a premium managed WordPress hosting company powered by Google Cloud Platform’s premium tier network and compute-optimized C2 virtual machines, enterprise-level security, a free CDN global edge network with 200+ PoPs, and 24/7/365 support.
👉Learn more about Kinsta’s hosting solutions: https://kinsta.com/wordpress-hosting/
⚙️Dig deeper in Kinsta’s tech stack and features: https://kinsta.com/features
👤Follow us:
► https://kinsta.com/blog/
► https://kinsta.com/newsletter/
► https://twitter.com/kinsta
► https://instagram.com/kinstahosting
► https://facebook.com/kinstahosting
__________________________
🕘Timestamps
0:00 Intro
1:12 Review Your CDN Settings
2:53 Check the Error Message for Specific Plugins
4:29 Disable (and Then Re-Enable) All of Your Plugins
6:44 Review Your .htaccess File
_________________________
📚 Resources
🛠 How to Resolve the “Remove Following Redirect Chain” Error (4 Methods)
► https://kinsta.com/blog/remove-the-fo…
#RedirectChain #RemoveFollowingRedirectChain
Content
0.355 -> (upbeat music)
1.188 -> Hello, I'm Maria.
2.021 -> And today I'm going to show you how to resolve
2.909 -> the "Remove Following Redirect Chain" error.
11.86 -> To keep your site in tiptop shape,
13.93 -> you need to test it regularly.
15.77 -> However, there's one GT metrics error message
19.04 -> that's been confusing WordPress website owners,
22.067 -> "remove the following redirect chain if possible."
25.05 -> In this video, we'll share four ways
27.38 -> to resolve this error
28.37 -> and get your WordPress website back on track.
31.56 -> But before we get too far, I wanna let you know
33.487 -> that there will be links to more resources
35.71 -> in the video's description
37.27 -> and remember subscribe
38.75 -> and ring that bell to get notifications
40.69 -> for few helpful content.
43.402 -> So let's get started
47.66 -> Frustratingly, this error can be due to a wide range
51.05 -> of different plugins, settings and third party software
54.31 -> such as firewalls.
56.07 -> While there's no one size fits all solution,
58.65 -> there are ways to chase
60.1 -> down the root cause for your particular website.
63.14 -> Let's take a look at how you can cut
64.93 -> through the confusion and strip away those performance
67.95 -> destroying redirect chains.
70 -> If you are using a CDN and firewall
72.2 -> your firewall may prevent the servers
74.37 -> from accessing your images.
76.34 -> If you suspect this may be the case we recommend
79.79 -> allow listing at the IP address on your CDN.
83.69 -> The allow listing process will vary depending
86.33 -> on the CDN and firewall in question.
89.04 -> So you may need to refer
90.36 -> to your provider's documentation for more information.
93.27 -> Similarly, your image files may not be publicly accessible.
97.25 -> For example, you might have password protected your website
100.78 -> or defined rules that are inadvertently
102.98 -> preventing the CDN from accessing your images.
106.1 -> If this sounds plausible, try disabling all settings
109.44 -> and rules that could block your CDN.
111.79 -> In particular, if you've created rules
114.34 -> to prevent hot linking
115.91 -> this can often interfere with CDNs resulting
119.16 -> in redirect chains.
120.58 -> Depending on your CDN subscription,
122.77 -> there's also a chance you may have exceeded
124.97 -> your monthly traffic quota.
126.92 -> When this occurs, some providers will redirect requests
129.705 -> to the original image resulting in chains.
134.115 -> To check your subscription status
135.22 -> try logging onto your CDN account or console.
138.64 -> You should see more information about your usage here.
141.91 -> If none of these solutions solve your problem
144.56 -> you may get positive results by flushing
146.92 -> the redirected images from your CDN.
149.27 -> The flushing process can vary,
150.86 -> but typically involves logging
152.57 -> into your provider's dashboard
154.39 -> or accessing the CDN plug-in settings.
157.2 -> You can then look for any options related to the cash.
160.27 -> If you're stuck,
161.23 -> it's a good idea to check the CDNs documentation
164.12 -> for more information, alternatively
167.09 -> you can always reach out to your provider for help.
169.55 -> It's also good to inspect the error message itself
172.65 -> as it may name the plugin responsible
174.84 -> for the redirect chain.
176.17 -> Take this example that a member
177.87 -> of the WordPress community posted
179.48 -> about receiving in GT metrics.
181.89 -> This message seems to indicate that the a3 Lazy Load plug in
185.55 -> is generating the redirect chains.
187.39 -> If your error message names
189.05 -> a specific plugin check to ensure
191.56 -> that you are running the latest release.
193.69 -> If you've fallen behind on updates
195.39 -> the developer may have already addressed this error
197.84 -> in a subsequent patch.
199.26 -> If you have the latest version,
200.79 -> the next step is reaching out to the plugins developer.
203.97 -> There's a chance they may be completely unaware
206.5 -> of the issue.
207.333 -> If you downloaded the plugin
208.83 -> from the official WordPress plugin directory
211.39 -> the listing should contain the name
213.03 -> of the person or team behind this particular plugin.
216.24 -> Even better, this page may contain
218.57 -> a link to the developer's website.
220.71 -> From there, you can often find their contact details.
224.14 -> Alternatively, each WordPress repository listing
227.21 -> contains a support tab.
228.97 -> By posting about your issue,
230.68 -> you may get help from the developer or even other users.
234 -> Ideally, if you manage to make contact
236.38 -> the developer will confirm that they're aware
238.53 -> of the problem or are already working on a patch.
241.37 -> However, it's not unusual for developers
243.89 -> to abandon their plug-ins, which can complicate matters.
247.91 -> If you suspect that this particular piece
250.09 -> of software is no longer under active development
253.37 -> you may need to disable it and look for an alternative.
256.6 -> The good news is that with almost 60,000 free plug-ins
259.91 -> in the WordPress repository alone
262.04 -> you should have no problems finding a suitable replacement.
265.35 -> Sometimes the error message may not
267.44 -> mention a specific plugin.
269.37 -> If GT metrics is vague,
271.33 -> then it's time to do your own investigative work.
274.66 -> You can check to see whether a plugin is responsible
276.98 -> by deactivating every plugin across your website.
280.38 -> If error message disappears,
282.48 -> you'll know that a WordPress plugin is to blame.
285.17 -> However, deactivating, these add-ons can affect
288.4 -> how your site displays and functions.
290.9 -> It's often bad news for the user experience.
294.31 -> For this reason, it's wise to place your site
297.4 -> into maintenance mode throughout the test.
299.71 -> If you don't feel comfortable
301.832 -> coding your maintenance message,
302.665 -> you can use a plugin
303.88 -> like WP Maintenance Mode.
306.22 -> For added security,
307.57 -> we also recommend creating a backup
309.83 -> before you begin switching your plugins off.
312.57 -> If you encounter any serious problems
315.2 -> this will prove invaluable
316.92 -> for restoring your site to its former configuration.
319.65 -> Your host may offer an automatic backup option
322.61 -> just like Kinsta does.
324.39 -> If not, there are multiple backup plugins
326.96 -> available that you can use instead.
328.66 -> Now that you're ready with a backup
330.26 -> and maintenance mode, you can disable your plugins.
333.55 -> This practice helps verify
335.2 -> whether a plugin is generating all of those redirects.
338.69 -> However, it would help
340.37 -> if you still pinpointed the exact culprit.
342.95 -> The next stage is reenabling each plugin one by one,
346.81 -> running a new GT metrics test after each.
350.27 -> As soon as the error reoccurs,
352.2 -> you'll have identified the misbehaving plugin.
354.82 -> It's not always feasible to deactivate
356.78 -> and delete a troublesome plugin though.
358.58 -> Maybe it's tied in too closely
360.57 -> with your website theme
361.99 -> or you aren't finding a good option
363.91 -> for a speedy replacement.
365.72 -> If this is the case, you might consider
367.97 -> contacting the developer.
369.73 -> They may be able to indicate when
371.44 -> you can expect a patch or perhaps even share a workaround.
375.04 -> For example, disabling a specific setting
378.08 -> may enable you to continue using the plugin
380.56 -> without encountering the redirect chain error.
383.06 -> However, sometimes the developer
385.11 -> may not intend to fix the issue,
387.25 -> mainly if the software is no longer
389.37 -> under active development,
390.98 -> if this is the case
392.3 -> it often makes sense to search
393.9 -> for an alternative that provides similar functionality
396.8 -> but doesn't spawn dozens of unnecessary redirects.
400.23 -> If you've previously set up redirects
402.27 -> or installed any add-ons that manage redirects for you,
405.9 -> then it's worth taking a look
407.24 -> at your site's htaccess file, short for hypertext access.
412.54 -> This is a critical configuration file created
415.14 -> automatically when installing WordPress.
417.46 -> Note that htaccess files are only available
420.29 -> on servers that run Apache,
421.176 -> and Gen X servers like those we run here at Kinsta,
425.06 -> don't have this Apache specific file.
427.65 -> Modifications to this file may occasionally result
430.8 -> in a large number of redirect chains.
433.5 -> Luckily, there are several ways to review this file,
436.78 -> including via a file manager
438.76 -> or controlled dashboard like cPanel.
441.55 -> You'll find the htaccess file
443.29 -> inside your website's public HTML folder.
446.41 -> Alternatively, you can connect to your server
448.85 -> over secure file transfer protocol using a client
452.21 -> such as FileZilla.
453.45 -> In the FileZilla client,
454.82 -> navigate to file and then site manager.
458.21 -> If you're connecting to your server
459.65 -> for the first time select new site.
462.5 -> You can then assign a name to this connection.
465.21 -> Enter a port value of 22,
467.33 -> if you're connecting by SFTP, otherwise enter 21.
471.56 -> Then you can open the log on type box
473.55 -> and select ask for password.
475.68 -> Next, enter your SFTP username and password.
479.2 -> Then click on the connect button.
481.48 -> All of your website's files should appear
483.61 -> in FileZilla's right hand window,
485.75 -> if the connection is a success.
487.89 -> In this panel navigate to your site's public HTML directory.
492.54 -> You should now have access to your htaccess file.
496.21 -> If you can't see,
498.353 -> you may need to elect to show hidden files first.
500.57 -> If you spot any unique code in this file,
502.87 -> it's a good idea to copy and paste this strange code
505.84 -> into your favorite search engine.
507.92 -> It's often the quickest and easiest way
510.09 -> to decipher what impact this code has on your website
513.25 -> and whether it might be behind all of those redirect chains.
516.8 -> There seems to be many different plugins
518.81 -> and settings that can result in redirect chains.
521.88 -> However, by following some simple steps
524.45 -> you can narrow down what's causing this problem
526.73 -> for your particular website.
528.38 -> Do you have any questions
529.35 -> about how to reduce redirects in WordPress?
531.48 -> Let us know in the comments section below.
535.52 -> An unsecured website puts your customers
537.548 -> and reputation at risk
539.74 -> with Kinsta's cloud flare integration
542.24 -> all the security features you need are built right
545.04 -> into your plan at no additional cost.
547.63 -> That's a monthly savings of around $200 per site.
551.23 -> Learn more about these benefits, including DDLs protection
555.38 -> a more secure firewall
556.827 -> and more at kinsta.com/cloudflare-integration.
563.01 -> Thank you so much for watching.
565.19 -> If you found this video helpful
567.18 -> please don't forget to like, subscribe
569.01 -> and hit that notification bell
570.73 -> for more tutorials, explainers
572.59 -> and helpful content like this.
Source: https://www.youtube.com/watch?v=oZ-Ha8wjSeU