Fix Block Page to load faster
beta / early access
Nick Saunders
beta / early access
We've released an improvement aimed at improving the performance of loading the Block Page when using a roaming client. As mentioned on this post, we've seen RC users experience slowness when loading the BP and we've introduced improved caching to improve loading times after an initial load on each fresh session.
Please share your experiences on the thread here. In our performance monitoring we've seen an easily noticeable improvement for RC users.
Nachman Weiss
Nick Saunders HI Nick, im running v 1.14.0.0 same issue as always ! Please Dont give up on fixing this !
Nachman Weiss
has anyone else seen any significant improvement ?
Nachman Weiss
Nick Saunders Hi Nick , its Sept 18 2024 , is this on the road map to get fixed ? its really embarrassing whenever I log on to someone's computer to troubleshoot a filtering issue I keep on saying that its being worked on but ive been saying the same thing for the past 5 years !
Steve Staden
Hello Voters, We do have an update to share here as we’ve been working with the engineering team. We have typically seen this slowness when Roaming Clients are being used. Given that, we’ve identified an issue that we’re working on and plan to deploy towards the end of April. We can provide another update once we’re closer to getting that released.
Nachman Weiss
Steve Staden Hi Steve, Thanks for the past update ! its already May 8th of 2024 are you able to please share with us any further Update?
Steve Staden
Nachman Weiss: Apologize for the delay here as it's taking a little bit longer than expected. Talking with the team we are planning to release this next week to our testing environment for validation. After that I should have a better idea on when this will then get released to production. I'll give another update later next week. Thanks for checking in on this one.
Steve Staden
Just wanted to provide another update, we just deployed to our test environment and will begin testing and provide a further update on how that testing went along with plans for deploying to production next week.
Nachman Weiss
Steve Staden Thanks Steve, i really appreciate that you are on top of this!
Steve Staden
Just wanted to provide another update, during our testing this week we identified an issue that we are working to address and will continue testing next week.
Nachman Weiss
Steve Staden Thanks Again Steve , really looking forward to seeing this resolved !
Nachman Weiss
HI Steve, Any update over here ?
Steve Staden
Nachman Weiss: Nothing yet, we're still having issues resolving what we found during testing. We are adding more instrumentation on our side to get better data, which we deployed this week, but will take some time to collect that information. Apologize for the delay.
Nachman Weiss
Steve StadenHI Steve , thanks for responding . can you please share what new issues were found during testing? this language sounds almost the same as i heard it 5 years ago! if you need help identifying the issue I'm more then happy help again (as ive done many times in the past )
Steve Staden
Nachman Weiss: Yes, we're seeing Chrome not loading correctly with the fixes we've put in. So, it's not
reproducing the issue, we're able to do that. Speaking of the fixes, we've reduced and also a cached a number calls to our backend, which we believe should improve performance.
Nachman Weiss
Happy 5th Anniversary This issue was reported 5 Years ago (or more) and was promised that a fix will be in place very soon !! am i the only one affected by it ?
Nachman Weiss
Attn: DNSFilter Developers Thanks for the wonderful Progress Thats been Made overall Please start working on this issue which has been reported over 4 years ago we know you can do it!!
Steve Staden
Nachman Weiss: Appreciate the feedback and glad you're seeing all the progress we're making! I'm going to discuss with the team and review your tickets to understand this better. I may need to follow-up with more details.
Nachman Weiss
Steve Staden: I'm ready whenever you are !
Jonathan Hozeska
This problem still exists. Both hosted and custom 302 redirect block pages take about 8 seconds to load. During the wait we see a circle of spinning dots. This issue is internal to DNSFilter and not related to the composure or location of the block page.
Nachman Weiss
Jonathan Hozeska: Please Be paitent It might just take another 4 years!
Jonathan Hozeska
Nachman Weiss:
The raw output from the redirect is listed here.
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>Website Filtered</title>
<style>
.container {
padding-top: 40px;
}
</style>
<link href="https://blockedv2.netalerts.io/main.css" rel="stylesheet"></head>
<body>
<div id="app"></div>
<script type="text/javascript" src="https://blockedv2.netalerts.io/index.js"></script></body>
</html>
The performance issue is linked to whatever magic is happening in the index.js. I'm not understanding why we first need to go to this intermediate page first. What is the reason for this?
Until that is fixed can't we just simply just have the redirect go directly to the raw redirect URL we are providing?
Jonathan Hozeska
Any update on this?
Jonathan Hozeska
Any update on this?
Steve Staden
Jonathan Hozeska: I apologize nobody responded previously to you, we aim to do better and will in the future. That said, I don't have any updates to share right now. I'm reviewing your ticket on this item and discussing with our team based on all the feedback here. We have been making improvements by adding additional resources. However, we're still investigating different areas that are causing the slowness around the block page. Unfortunately, this issue is not one that can be solved easily. We believe there is more complex architecture change that is required to see more meaningful improvements that we're currently evaluating. Also, happy to discuss with you further, my email is [email protected].
Aliese
under review ( scoping )
Thank you for your feedback!
We have opened a ticket with our Engineering team to look into this issue. We will provide feedback and updates here as it's available!
Nachman Weiss
Aliese: HI a ticket has been opened for this issue over 3 years ago and still not been resolved
Aliese
Nachman Weiss: Our Engineering team is actively looking into this. After they complete their initial investigation, we'll be in touch with more details. Thank you for your feedback and patience!
Nachman Weiss
Aliese: HI Another Year went by and still no progress! this is a Total Disgrace! i reported this issue in 2019 and was told that its a known issue and that they are working on it !!
Nick Saunders
Nachman Weiss: Hi Nachman, appreciate your frustration on updates here - we have made updates that were posted on this item, including better scalability for high block page traffic that was released in February 2023 - the block page should be loading in <7.5sec in nearly all cases. If you are seeing otherwise I'll ask Support to reach out so we can gather additional details. That said we do want to continue improving the block page performance and functionality. A few other features we're considering are improvements to BP bypass and a non-SSL version of the block page.
Nachman Weiss
Nick Saunders: Hi Nick ,Thanks for Responding 1. nothing was done that resolved the issue with the slow loading of the block page (the article that you mentioned from February 2023 https://dnsfilter.canny.io/changelog/updated-block-page-ip-addresses is about the Ip addresses getting updated
- 7.5 seconds for a block page to load is the issue that were dealing with which is unacceptable
- it takes about 10 seconds to load a block page i really didn't want to mention number 3 since its irrelevant
there's no reason that it should take more then .5 second
just like it loads instantly when the window's roaming client is not installed.
i have over the past year alone opened many support tickets about this issue but no results