Member Avatar for johnkafy

Hello Evreyone,

I Faced a big problem, I have a Instagram Service site, but this speed is low, I'm trying some time but faild to raise site speed, see site speed https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fbuyfastlike.com%2F&tab=mobile

Site url - https://buyfastlike.com

Edited by happygeek because: deleted duplicate site url links
  • 7 Contributors
  • 6 Replies
  • 468 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by Halla_1

Dani AI

Generated

A short, practical checklist and targeted fixes to complement the replies already here (noting ’s WOT observation and the general advice from , , , and ).

Start with a measurement baseline (mobile + desktop, from relevant regions): run WebPageTest and a Lighthouse run from Chrome DevTools. Record TTFB, Start Render / First Contentful Paint, Largest Contentful Paint and Total Blocking Time. If TTFB is high, the problem is server/back-end; if asset times dominate, the problem is front-end.

High-impact back-end checks (often overlooked)

  • Confirm PHP is a recent, supported build and enable OPcache / PHP-FPM.
  • Capture slow PHP/MySQL queries (enable slow query log or use New Relic/Query Monitor) and add missing indexes or rewrite expensive queries.
  • Use server-side object caching (Redis/Memcached) and ensure PHP worker limits on the host match traffic.
  • Scan for hidden cron jobs or excessive external API calls (Instagram/payment endpoints) that serialize requests.

Front-end fixes (low-friction wins)

  • Convert and serve images as WebP/AVIF with responsive srcset, and use native lazy loading (loading="lazy") for offscreen images.
  • Inline critical CSS for above-the-fold content; defer or async noncritical JS and remove render-blocking fonts. Use font-display: swap and subset fonts.
  • Audit third‑party scripts and defer or host them locally when feasible. Preconnect/preload only the most critical origins.

Two quick WordPress snippets for staging (test each change on a staging site):

Disable the Heartbeat API on the frontend:

add_action( 'init', function() {
    if ( ! is_admin() ) {
        wp_deregister_script( 'heartbeat' );
    }
}, 1 );

If WooCommerce is present, stop cart-fragment AJAX (test cart behavior first):

add_action( 'wp_enqueue_scripts', 'dequeue_woocommerce_cart_fragments', 11 );
function dequeue_woocommerce_cart_fragments() {
    wp_dequeue_script( 'wc-cart-fragments' );
}

A safe troubleshooting order: 1) baseline with WebPageTest/Lighthouse; 2) reproduce on a staging copy; 3) profile plugins/themes (Query Monitor) and disable the heaviest item; 4) apply one back-end change (PHP/OPcache or DB tune) and retest; 5) apply front-end optimizations and retest. Log each change and its metric impact.

Recommended Answers

All 6 Replies

Member Avatar for rproffitt

I'd fix your Web Of Trust issues first. WOT blocked your site so I couldn't check it out.

Member Avatar for Hemant_7

Remove unwated default wordpress code, Work on google page insight and GTMETRIX...

Edited by happygeek because: spam deleted - please use signature facilty
Member Avatar for agustina

Remove unwanted codes in your WordPress

Member Avatar for Dani

There are some WordPress plugins for caching and SEO that should help. It might also be your hosting provider causing slowness.

Member Avatar for Trasser

The problem may lie in the code, caching or hosting.

Member Avatar for Halla_1

The problem with hosting is easy to find or disprove using special tools https://www.host-tracker.com/ Setting up normal caching is also not difficult. If the problem is in the code or topic, then you have to work on fixing the problem.

Edited by Halla_1
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.