Blog
Web performance
Posts about Web performance.
-
Most AI crawlers do not run JavaScript, so client-side content can be invisible to them
DEV Community reports that most AI crawlers read only raw HTML, so content added by JavaScript may never reach them, unlike with Google.
-
Why Google leaves pages as 'Discovered – currently not indexed' and how to fix it
A DEV Community guide explains what the Search Console status means, five likely causes, and which common fixes waste time.
-
JTL-Shop 5 speed: four common mistakes that slow down page loading
A DEV Community guide lists four typical JTL-Shop 5 speed mistakes, from old PHP and no object cache to a lazy-loaded main image and idle plugins.
-
Turkish WordPress guide lists four causes of site faults and a four-step fix routine
A DEV Community post from wordpressuzmani.com covers causes of WordPress faults, from PHP limits to broken config files, with four fix steps.
-
Site audit finds the srcset habit misses the real image problems
A DEV Community audit of one production site found lazy loading, screen maths and file format mattered more than adding srcset to every image.
-
A/B testing and SEO: review the temporary redirect and cleanup plan before launch
A DEV Community guide says to check redirects, canonical links and a cleanup plan before launching an A/B test on public pages.
-
How to compare CMS speed fairly using public PageSpeed and tech stack data
A DEV Community guide shows how to compare platforms like WordPress and Shopify on PageSpeed scores, and why the results should not be over-read.
-
Deferring Google Tag Manager until first interaction cut third-party blocking time to zero on a Next.js site
A team moved all marketing tags behind the first visitor interaction on their Next.js homepage and cut third-party blocking time from 4,335 ms to 0 ms.
-
A PNG saved with a .webp filename cost one services page 441 KiB on mobile
A site owner found a PNG disguised as WebP, rebuilt it as a real WebP, and lifted a mobile PageSpeed score from 72 to 85, per DEV Community.
-
A five-step order for fixing Core Web Vitals on a marketing site
A DEV Community post sets out five fixes for slow marketing sites, from measuring first to the largest image, blocking scripts, layout shifts and interaction.
-
How to build a store 404 page that is honest with search engines and useful to shoppers
A DEV Community guide says a store's 404 page has two jobs: return a real 404 status for crawlers, and help shoppers find what they wanted.
-
Safari 27.3 beta may darken light sites that don't declare a color scheme
Safari 27.3 beta can repaint light pages in dark colours for users on dark systems. One color-scheme line decides whether your site is touched.
-
Landing page photos were JPEGs renamed .webp, and two went to visitors at full size
A DEV Community post details three JPEGs renamed .webp, mislabelled by the server, and two served unoptimised through CSS backgrounds at 1.87 MB.
-
Next.js image defaults allow 15 widths, one quality and no AVIF unless you change them
A DEV Community post probes the default Next 16.2.7 image endpoint and finds fixed widths, one quality, WebP only and a revalidating cache header.
-
Developer guide: choosing and shipping business website images that stay fast
DEV Community guide covers picking real photos, sizing, WebP, compression, alt text, licensing and responsive image code for faster business sites.
-
Stripping WebP from Chrome's Accept header mostly just gets you AVIF, test finds
A DEV Community test of five image hosts found that removing WebP from the Accept header usually returns AVIF, not JPEG, on large image CDNs.
-
Font preloads delayed first paint by 3.7 seconds on a slow connection, a developer's tests show
A DEV Community post finds ten font preloads slowed first paint on a throttled link and caused a late layout shift, then explains the fixes the author plans.
-
Which product grid images should never be lazy loaded, according to DEV Community
A DEV Community post explains which images on store pages should load straight away, and which can wait until the visitor scrolls.
-
AVIF first, WebP as fallback is the advice for image-heavy product pages
A DEV Community post says image-heavy sites should serve AVIF first with WebP as fallback, and test both formats on their own fine-texture images.
-
Why lab scores and CrUX field data can differ when page loads are incomplete
A DEV Community post explains why a green lab score and an amber field score can both be right, and how partial loads and navigation types shape CrUX data.
-
Reserve space for images before they load to stop text jumping
DEV Community explains how width and height attributes let browsers reserve room for a photo, so text below it stays put while the file downloads.