Why your website is slow on a phone

First, see which of the three is holding up your home page

Run your domain on kortaga.com/check to see whether your server took more than 2.5 seconds to start answering (slow-ttfb) or whether your home page downloads more than 4 MB on first load (heavy-page). To see the exact file sizes in your browser:

1. Open your home page in Chrome or Firefox on a computer, press F12, and click the Network tab.
2. Check Disable cache at the top of the Network panel and reload the page.
3. Look at the bottom summary bar for total transferred megabytes and click the Size column header to sort largest files first. On a phone over cellular data, every megabyte above 1 MB adds roughly one to two seconds of blank or jumping screen.

1. Shrink oversized hero photos to WebP and lazy-load images below the fold

A raw photo exported from a phone or camera is often 3 MB to 8 MB and 4000 pixels wide, even though a phone screen is only 390 to 430 CSS pixels wide.

1. Resize your top banner (hero) image to at most 1600px wide (and a 800px copy for phones) and convert it to WebP or AVIF at quality 78 to 82. A 4 MB JPEG typically drops under 120 KB with no visible loss on a phone screen.
2. Keep the top banner image eager so it paints immediately, and add loading="lazy" and explicit width and height attributes to every image further down the page so the phone only downloads them when the visitor scrolls:<img src="/img/shop-front-800.webp" srcset="/img/shop-front-800.webp 800w, /img/shop-front-1600.webp 1600w" sizes="(max-width: 768px) 100vw, 800px" width="1600" height="1000" alt="Front counter at Broadway Auto"> <img src="/img/bay-two-800.webp" width="800" height="600" loading="lazy" decoding="async" alt="Service bay two">

2. Defer render-blocking scripts and third-party widgets

When a browser meets a plain <script src="..."> tag inside <head> without defer or async, it stops building the page, downloads the script, and runs it before drawing a single word of your headline.

1. Add defer to your own scripts in <head> so the browser downloads them in the background and runs them after the HTML is parsed:<script src="/app.js" defer></script>
2. Audit third-party widgets (live chat bubbles, heatmap recorders, social feed embeds, and multiple analytics tags). Each chat or review widget often loads 500 KB to 1.5 MB of JavaScript on a phone. Remove any widget that has not brought you a customer in the last 30 days, or load it only when the visitor taps a button.

3. Fix a slow server response (Time to First Byte over 2.5 seconds)

If your files are small but the browser waits several seconds before the very first byte of HTML arrives, your server is running database queries and PHP templates on every single visit instead of serving a saved copy.

1. If your site runs on WordPress, turn on full-page caching in your host's control panel (or enable a single lightweight page-cache plugin) so repeat visitors get pre-built HTML in under one-tenth of a second.
2. Check your PHP version in your hosting dashboard: upgrading from PHP 7.4 to PHP 8.2 or 8.3 typically cuts WordPress server response time in half.
3. If your business site only shows your services, hours, photos, address, and phone number, static HTML served from a CDN edge opens in under a tenth of a second worldwide with zero database or plugin overhead.

These steps follow MDN's guides on HTML performance features, Lazy loading, the script element (async and defer), and Time to first byte (TTFB), all read 28 October 2026.

If you would rather we write it or repair it for you