Hostinger Hosting

Ads Zone said:

Where are you getting these errors?

Click to expand...

ghost666 said:

Ideally, your web page should load in less than 2 seconds; if it loads within 2 seconds, then disregard all these minor suggestions.

Click to expand...

digihub said:

Try this: detect slow queries and PHP bottlenecks (Query Monitor/New Relic), set up object caching with Redis, bump PHP-FPM/OPcache settings, add a CDN with HTTP/2, switch to a lightweight Nginx/OpenLiteSpeed server, and use PHP 8.1. These tweaks should get your TTFB below 500 ms.

Click to expand...

• Query Monitor: This is my immediate next step. I'm keen to see if a specific query is the bottleneck.
• Object Caching (Redis): That's a great shout. While this specific shared plan from Hostinger likely doesn't support Redis, it's a technique I use for more demanding client projects to great effect.
• CDN & PHP: I'm already on PHP 8.1 and using Cloudflare's CDN, which handles HTTP/2. I'll check what I can do about OPcache settings, though they might be locked down on this plan.

Roko said:

How many plugins you are using, did you optimize the images?

Click to expand...

Rasel Pathan said:

This is fantastic, exactly the kind of high-level technical feedback I was hoping for. Thank you for taking the time to write this out.

Here's my situation regarding your points:

• Query Monitor: This is my immediate next step. I'm keen to see if a specific query is the bottleneck.
• Object Caching (Redis): That's a great shout. While this specific shared plan from Hostinger likely doesn't support Redis, it's a technique I use for more demanding client projects to great effect.
• CDN & PHP: I'm already on PHP 8.1 and using Cloudflare's CDN, which handles HTTP/2. I'll check what I can do about OPcache settings, though they might be locked down on this plan.

Your suggestion about Nginx/OpenLiteSpeed confirms my suspicion that the server stack itself is the primary limitation here. To get the sub-500ms TTFB I aim for on my projects (like the ones on raselpathan.site), a more powerful and configurable hosting environment seems to be the answer.

Really appreciate the solid checklist.

Click to expand...

Rasel Pathan said:

Sorry for the late reply, this is a screenshot of Google Page Speed Insight.

Click to expand...

Rasel Pathan said:

You're absolutely right, the 2-second benchmark for total page load is a critical goal. Thanks for highlighting that.The nuance here, and the core of my issue, is that the 2206ms figure isn't the full page load time—it's just the initial server response time (Time to First Byte or TTFB). This means the final page load time is significantly longer once all the content, scripts, and styles are rendered.For the affiliate sites I build for clients (affiliated website at darman.store), I always aim for a TTFB under 400ms. A TTFB over 2000ms is a major bottleneck that needs to be fixed at the source before any front-end optimization can be effective. Appreciate the input!

Click to expand...

Rasel Pathan said:

This is fantastic, exactly the kind of high-level technical feedback I was hoping for. Thank you for taking the time to write this out.

Here's my situation regarding your points:

• Query Monitor: This is my immediate next step. I'm keen to see if a specific query is the bottleneck.
• Object Caching (Redis): That's a great shout. While this specific shared plan from Hostinger likely doesn't support Redis, it's a technique I use for more demanding client projects to great effect.
• CDN & PHP: I'm already on PHP 8.1 and using Cloudflare's CDN, which handles HTTP/2. I'll check what I can do about OPcache settings, though they might be locked down on this plan.

Your suggestion about Nginx/OpenLiteSpeed confirms my suspicion that the server stack itself is the primary limitation here. To get the sub-500ms TTFB I aim for on my projects (like the ones on raselpathan.site), a more powerful and configurable hosting environment seems to be the answer.

Really appreciate the solid checklist.

Click to expand...

Rasel Pathan said:

Thanks for asking. I'm running about 8 essential plugins right now. And yes, all images are fully optimized and served in WebP format.

I've already done the test of disabling all plugins, but the slow server response time (TTFB) persisted. This leads me to believe the root cause isn't related to plugins or images, but is deeper within the server configuration.

Click to expand...