[Nishit Shan]

in reply to: Custom Works #15859

Hello Andrey,

This is my finding i was making from last 3 days:

Issue Report
I have reviewed the project structure, homepage flow, theme, and settings. Based on this analysis, there are a few key reasons why the site feels slow and why some information may appear inconsistent.

Main Issues Identified
1. Heavy Page Loading
• Multiple database queries are being executed on almost every page load.
• A large number of front-end scripts are being loaded globally, even on pages where they are not required.
• Impact: Increased load times, especially on the homepage and theme-based pages.

2. Content Sourced from Multiple Layers
• Page content is being managed across different sources, including:
◦ Page builder
◦ Theme files
◦ APIs
◦ Custom database queries
• When updates are made in one place without proper synchronization, outdated or inconsistent data may be displayed.

3. Outdated Platform Architecture
• The application is currently running on an older version of Laravel.
• Upgrading to a newer version (e.g., Laravel 13) will require a structured migration process rather than a direct version update.
• Several third-party packages may not be compatible with newer versions and will require updates or replacements.

Required Updates & Improvements
1. Core Platform Upgrade
• Upgrade the application step-by-step from the current Laravel version to a modern compatible stack, eventually reaching Laravel 13.
• This process will require careful migration, testing, and validation at each stage.

2. Server Environment Update
• Upgrade PHP to version 8.3 or higher to support newer Laravel versions.
• Ensure all required server extensions and configurations are aligned with the updated framework.

3. Dependency Management
• Review all existing packages and libraries.
• Update compatible packages and replace outdated or unsupported ones with modern alternatives.

4. Performance Optimization
• Minimize unnecessary processing during page load.
• Implement caching strategies where applicable.
• Load front-end assets conditionally, only where needed.

Additional Note
API integration will require rework using a modern approach. The current implementation relies on outdated methods that are not optimized and contribute to slower execution. Refactoring this layer will be necessary to improve overall performance and maintain compatibility with the upgraded system.

Conclusion
The issues identified are primarily related to architectural limitations, outdated dependencies, and inefficient resource handling. Addressing these through a structured upgrade and optimization plan will significantly improve performance, maintainability, and scalability.

[Nishit Shan]

in reply to: Custom Works #15857

Hello Andrey,

Sorry, I noticed that I mistyped in my earlier message. I mentioned 9 lakh+ data, but I forgot to add the “1” before 9. The correct total is 1,969,082 records.

Out of this, 166,772 + 180,829 + 186,482 + 145,350 + 179,605 + 116,642 = 975,680 records are unnecessary. However, I can assure you that these 975,680 records are not being used or accessed, so they are not affecting the loading performance. Therefore, this is not a concern at the moment. I just wanted to inform you so you are aware of it.

The investigation is taking longer than expected and requires more in-depth research. I may also need to discuss this with my boss and accounts team. If they approve, I will proceed further. I had not informed them earlier because I initially thought this would not take much time, but it is now becoming more time-consuming.

As a suggestion, the newer versions of Laravel have introduced structural changes starting from version 10, and the current version is Laravel 13. Whenever you plan to upgrade, I would recommend not doing just a surface-level update. Instead, align the application with the updated framework structure so that it performs optimally. This may also help improve performance.

This is just my suggestion, and I am open to proceeding based on your recommendation as well.

[Nishit Shan]

in reply to: Custom Works #15853

Hello Andrey,

I am still reviewing your code and also using AI tools to analyze it. I will share my feedback once the review is complete.
So far, I haven’t found anything additional, but I haven’t finished the review yet.

[Nishit Shan]

in reply to: Custom Works #15851

Hello Andrey,

I was reviewing the application to understand the existing and current working functionality as a precautionary measure. During this review, I noticed that the page https://portal.voip.us/user-home is not loading properly and keeps loading continuously without displaying content.

Since I have previously worked on this module, one possible reason could be the large size of the database, which currently contains approximately 9 lakh+ records. This may be impacting performance. Additionally, multiple API calls involved in loading this page could also be contributing to the issue.

Another important observation is that the project is still running on Laravel 8, which is around 5 years old. This version no longer receives regular updates or active support, which may also be a factor in the current performance and stability issues.

I wanted to highlight these points to keep you informed, as some of these issues might persist even after certain changes are made.

To improve performance and stability, it would be advisable to upgrade the framework to a newer version and optimize the existing codebase accordingly.

I am still in the process of reviewing the project, and these are my initial findings that I felt were important to share.

[Nishit Shan]

in reply to: Content Improvment #15848

Hello Andrey,

You can disconnect my access to Excellent Number. There was a tem_vid folder containing some videos that I had shared for reference, which I have now deleted. I also had some backup files stored for safety for a month, which i keep for safety.

I will review the other tasks you’ve assigned related to VoIP and will get back to you with my points and understanding.

[Nishit Shan]

in reply to: Content Improvment #15825

Hello Andrey,

Any update or any new task i need to view ?

[Nishit Shan]

in reply to: Content Improvment #15822

Hello Andrey,

Nice catch , actually it was admin side issue which was not showing many IP based on the flag (condition) . I have fixed this and now it is showing .

[Nishit Shan]

in reply to: Content Improvment #15813

Hello Andrey,

I have reviewed the nanotel code and also checked the logs where I record any issues that occur during execution.

If something like this happens again in the future— which I do not expect— please ask the admin to provide the exact date and time of the incident so I can investigate it more effectively.

[Nishit Shan]

in reply to: Content Improvment #15807

Hello Andrey,

I have been investigating this from our side and am still looking into the Nanotel issue. However, you mentioned that users are unable to place orders from the CLEC page. I tested it and was able to successfully place an order.
You can refer screen recorded video link for reference:
[video src="https://excellentnumbers.com/temp_vid/Screencast%20from%202026-06-11%2009-37-04.mp4" /]

I am continuing to check the Nanotel part.

[Nishit Shan]

in reply to: Content Improvment #15803

Hello Andrey,

I will check this and update you. However, I don’t believe the issue is from our side. I will still test it on my end and get back to you as soon as possible.

[Nishit Shan]

in reply to: Content Improvment #15801

Hello Andrey,

I have used the same template that was used previously. Please check the screenshot for your quick reference: https://ibb.co/BKySYZ5N

[Nishit Shan]

in reply to: Content Improvment #15797

Hello Andrey,

I have made design changes and added a dropdown. Please check the contact form submission as well as the design.

I tested it using my own email address, and I received the email successfully. Please verify that all respective departments are receiving the emails correctly.

Also, review the design. It looks good to me, but feel free to suggest any improvements if needed.

Please refer to the screen-recorded video for reference:
[video src="https://excellentnumbers.com/temp_vid/Screencast%20from%202026-06-10%2011-57-56.mp4" /]

[Nishit Shan]

in reply to: Content Improvment #15789

Hello Andrey,

Just an update: Working on contact us page for responsive design and selection based email .

For the nanotel , i will check once i complete this because i don’t want to leave it in half way .

• This reply was modified 1 week, 3 days ago by Nishit Shan.

[Nishit Shan]

in reply to: Content Improvment #15785

Hello Andrey,

Thank you for your advice regarding the Contact Us page.

Regarding the Nanotel issue, I can assure you that none of our recent changes to the Excellent Number module are related to it, and therefore would not have any impact on Nanotel.

Although I was already confident about this, I reviewed the Excellent Number code again and found no connection. I would also like to confirm that I have not made any changes to the Nanotel code for over a year, possibly even longer.

I kindly request that you do not delete the developer account. I have access to the registered email and will complete the verification.

[Nishit Shan]

in reply to: Content Improvment #15781

Hello Andrey,

I have fixed the issue with the account.php URL, and it is now working properly. I have also hidden the unnecessary content from the mynumber URL. The issue was caused because part of the mynumber module code was being displayed there.

I also encountered a strange issue. As a precaution, I usually comment out code instead of removing it permanently. However, I noticed that the commented code was still partially executing internally, running incomplete queries and affecting the overall design and layout.

Please check the video for reference i have also included customer lsit part of admin side : https://excellentnumbers.com/temp_vid/Screencast%20from%202026-06-05%2010-37-19.mp4

[Author]

Posts