Author name: Carrie Carlson

If you are tired of installing bulky SEO plugins just to display a simple navigation trail, you are in the right place. In this tutorial, we will show you exactly how to add WordPress breadcrumbs without a plugin, using only PHP inside your theme’s functions.php file, plus proper JSON-LD schema markup so Google can display them in search results. This method is lightweight, fast, and gives you full control over the HTML output. No plugin bloat, no unnecessary database queries, just clean code that works. Why Code Breadcrumbs Instead of Using a Plugin? Plugins like Yoast or RankMath do offer breadcrumb features, but they come with a full ecosystem you might not need. Here is a quick comparison: Aspect Plugin Method Custom PHP Method Performance Extra queries and assets loaded Minimal footprint Customization Limited to plugin options Full control over HTML and CSS Schema Markup Often included but generic Tailored JSON-LD output Dependencies Tied to plugin updates Independent, portable code Step 1: Add the Breadcrumb Function to functions.php Open your child theme’s functions.php file (never edit the parent theme directly) and paste the following function. It handles posts, pages, categories, tags, custom post types, author archives, search results, and 404 pages. function express_custom_breadcrumbs() { $separator = ‘»’; $home_title = ‘Home’; $home_url = home_url(); global $post; $output = ‘<nav class=”express-breadcrumbs” aria-label=”Breadcrumb”>’; $output .= ‘<a href=”‘ . $home_url . ‘”>’ . $home_title . ‘</a> ‘ . $separator . ‘ ‘; if ( is_category() ) { $output .= single_cat_title(”, false); } elseif ( is_tag() ) { $output .= single_tag_title(”, false); } elseif ( is_author() ) { $output .= ‘Author: ‘ . get_the_author(); } elseif ( is_search() ) { $output .= ‘Search results for: ‘ . get_search_query(); } elseif ( is_404() ) { $output .= ‘Page not found’; } elseif ( is_single() ) { $post_type = get_post_type(); if ( $post_type != ‘post’ ) { $pt_obj = get_post_type_object($post_type); $output .= ‘<a href=”‘ . get_post_type_archive_link($post_type) . ‘”>’ . $pt_obj->labels->singular_name . ‘</a> ‘ . $separator . ‘ ‘; } else { $categories = get_the_category(); if ( $categories ) { $cat = $categories[0]; $output .= ‘<a href=”‘ . get_category_link($cat->term_id) . ‘”>’ . $cat->name . ‘</a> ‘ . $separator . ‘ ‘; } } $output .= get_the_title(); } elseif ( is_page() ) { if ( $post->post_parent ) { $ancestors = array_reverse(get_post_ancestors($post->ID)); foreach ( $ancestors as $ancestor ) { $output .= ‘<a href=”‘ . get_permalink($ancestor) . ‘”>’ . get_the_title($ancestor) . ‘</a> ‘ . $separator . ‘ ‘; } } $output .= get_the_title(); } $output .= ‘</nav>’; return $output; } Step 2: Display the Breadcrumbs in Your Theme Now you need to call this function where you want the breadcrumbs to appear. Typical locations include: header.php – right below the main navigation single.php – above the post title page.php – above the page content archive.php – above the archive listing Add this line where you want the trail to appear: <?php echo express_custom_breadcrumbs(); ?> Using a Shortcode Instead If you prefer inserting breadcrumbs via the block editor or a widget, register a shortcode: function express_breadcrumbs_shortcode() { return express_custom_breadcrumbs(); } add_shortcode(‘breadcrumbs’, ‘express_breadcrumbs_shortcode’); Then simply use [breadcrumbs] anywhere in your content. Step 3: Add Schema Markup for SEO This is where most tutorials stop, but Google needs structured data to actually display breadcrumbs in the search snippet. We will use JSON-LD BreadcrumbList schema, the format Google officially recommends. Add this function to your functions.php: function express_breadcrumbs_schema() { if ( is_front_page() ) return; $items = array(); $position = 1; $items[] = array( ‘@type’ => ‘ListItem’, ‘position’ => $position++, ‘name’ => ‘Home’, ‘item’ => home_url() ); if ( is_single() ) { $categories = get_the_category(); if ( $categories ) { $cat = $categories[0]; $items[] = array( ‘@type’ => ‘ListItem’, ‘position’ => $position++, ‘name’ => $cat->name, ‘item’ => get_category_link($cat->term_id) ); } $items[] = array( ‘@type’ => ‘ListItem’, ‘position’ => $position++, ‘name’ => get_the_title(), ‘item’ => get_permalink() ); } elseif ( is_page() ) { global $post; if ( $post->post_parent ) { $ancestors = array_reverse(get_post_ancestors($post->ID)); foreach ( $ancestors as $ancestor ) { $items[] = array( ‘@type’ => ‘ListItem’, ‘position’ => $position++, ‘name’ => get_the_title($ancestor), ‘item’ => get_permalink($ancestor) ); } } $items[] = array( ‘@type’ => ‘ListItem’, ‘position’ => $position++, ‘name’ => get_the_title(), ‘item’ => get_permalink() ); } elseif ( is_category() ) { $items[] = array( ‘@type’ => ‘ListItem’, ‘position’ => $position++, ‘name’ => single_cat_title(”, false), ‘item’ => get_category_link(get_queried_object_id()) ); } $schema = array( ‘@context’ => ‘https://schema.org’, ‘@type’ => ‘BreadcrumbList’, ‘itemListElement’ => $items ); echo ‘<script type=”application/ld+json”>’ . wp_json_encode($schema) . ‘</script>’; } add_action(‘wp_head’, ‘express_breadcrumbs_schema’); Step 4: Style Your Breadcrumbs Add this to your theme’s style.css file to make the breadcrumbs look clean and readable: .express-breadcrumbs { font-size: 14px; color: #666; padding: 12px 0; margin-bottom: 20px; } .express-breadcrumbs a { color: #0073aa; text-decoration: none; } .express-breadcrumbs a:hover { text-decoration: underline; } Step 5: Test Your Breadcrumbs Before considering the job done, run through these checks: Visit a post, a page, a category archive, and a 404 page. Confirm the trail matches the actual hierarchy. Open the page source and verify the JSON-LD script is present in the <head>. Use the Google Rich Results Test at search.google.com/test/rich-results to validate the BreadcrumbList schema. Check the Schema Markup Validator at validator.schema.org for any warnings. Submit the updated pages via Google Search Console to speed up re-indexing. Handling Custom Post Types and Taxonomies The function above already handles custom post types by pulling the archive link. If your CPT uses a custom taxonomy (like a WooCommerce product with product categories), extend the is_single() block like this: if ( is_singular(‘product’) ) { $terms = get_the_terms(get_the_ID(), ‘product_cat’); if ( $terms && !is_wp_error($terms) ) { $term = array_shift($terms); $output .= ‘<a href=”‘ . get_term_link($term) . ‘”>’ . $term->name . ‘</a> ‘ . $separator . ‘ ‘; } } Common Mistakes to Avoid Editing the parent theme directly. Your changes will be lost on the next update. Always use a child theme. Duplicating schema. If another plugin already outputs BreadcrumbList schema, remove one of them to avoid conflicts. Forgetting the aria-label. Accessibility matters, and screen readers rely on

A filterable image gallery in JavaScript is one of those UI patterns that looks simple on the surface but hides a lot of small decisions: how to structure your tags, how to animate transitions, how to keep it accessible on mobile, and how to add sorting without pulling in a heavy library. In this tutorial we will build one from scratch using vanilla JavaScript, CSS Grid and a few modern browser features. No jQuery, no Isotope, no framework. By the end you will have a gallery that filters by category, sorts by date or name, animates smoothly, and works well on phones. What we are building A responsive image grid powered by CSS Grid Category filter buttons (with support for multiple tags per image) A sort dropdown (newest, oldest, alphabetical) Smooth fade and scale transitions when items enter or leave A mobile-friendly layout with touch-safe controls Unlike the classic W3Schools portfolio gallery, this version uses data attributes for tags, supports combined filters, and adds sorting, which most tutorials skip. Step 1: The HTML structure We start with a clean semantic structure. Each image card carries its metadata inside data attributes, which is what makes filtering and sorting trivial later. <div class=”gallery-controls”> <div class=”filters”> <button class=”filter-btn active” data-filter=”all”>All</button> <button class=”filter-btn” data-filter=”nature”>Nature</button> <button class=”filter-btn” data-filter=”city”>City</button> <button class=”filter-btn” data-filter=”people”>People</button> <button class=”filter-btn” data-filter=”food”>Food</button> </div> <select id=”sort” class=”sort-select”> <option value=”newest”>Newest first</option> <option value=”oldest”>Oldest first</option> <option value=”az”>A to Z</option> <option value=”za”>Z to A</option> </select> </div> <div class=”gallery” id=”gallery”> <figure class=”item” data-tags=”nature” data-date=”2026-03-14″ data-title=”Forest”> <img src=”forest.jpg” alt=”Forest”> <figcaption>Forest</figcaption> </figure> <figure class=”item” data-tags=”city people” data-date=”2026-05-02″ data-title=”Street”> <img src=”street.jpg” alt=”Street”> <figcaption>Street</figcaption> </figure> <!– more items –> </div> Notice how data-tags can hold multiple values separated by spaces. That is the key to letting one image belong to several categories. Step 2: The CSS Grid layout CSS Grid handles the responsive layout with a single line. No media queries required for the basic flow. .gallery { display: grid; grid-template-columns: repeat(auto-fill, minmax(220px, 1fr)); gap: 16px; } .item { margin: 0; overflow: hidden; border-radius: 12px; background: #111; position: relative; transition: transform .35s ease, opacity .35s ease; } .item img { width: 100%; height: 220px; object-fit: cover; display: block; } .item.hide { opacity: 0; transform: scale(.85); pointer-events: none; position: absolute; width: 0; height: 0; } .filter-btn { padding: 8px 16px; border-radius: 999px; border: 1px solid #ddd; background: #fff; cursor: pointer; } .filter-btn.active { background: #111; color: #fff; } The .hide class is what animates items out. We do not use display: none because it kills transitions. (via https://dev.to) Step 3: The filtering logic in vanilla JavaScript Here is the core filter function. It reads the active filter, checks each item’s tag list, and toggles the hide class. const gallery = document.getElementById(‘gallery’); const items = Array.from(gallery.querySelectorAll(‘.item’)); const buttons = document.querySelectorAll(‘.filter-btn’); let currentFilter = ‘all’; function applyFilter(filter) { currentFilter = filter; items.forEach(item => { const tags = item.dataset.tags.split(‘ ‘); const match = filter === ‘all’ || tags.includes(filter); item.classList.toggle(‘hide’, !match); }); } buttons.forEach(btn => { btn.addEventListener(‘click’, () => { buttons.forEach(b => b.classList.remove(‘active’)); btn.classList.add(‘active’); applyFilter(btn.dataset.filter); }); }); Step 4: Adding the sort feature Sorting is where most tutorials stop short. We simply reorder the DOM nodes based on the selected criteria. const sortSelect = document.getElementById(‘sort’); function applySort(mode) { const sorted = […items].sort((a, b) => { if (mode === ‘newest’) return b.dataset.date.localeCompare(a.dataset.date); if (mode === ‘oldest’) return a.dataset.date.localeCompare(b.dataset.date); if (mode === ‘az’) return a.dataset.title.localeCompare(b.dataset.title); if (mode === ‘za’) return b.dataset.title.localeCompare(a.dataset.title); }); sorted.forEach(node => gallery.appendChild(node)); } sortSelect.addEventListener(‘change’, e => applySort(e.target.value)); Because CSS Grid respects source order, re-appending the nodes is enough. No manual positioning needed. Step 5: Smooth transitions with the FLIP technique If you want the items to animate to their new positions when sorting, use the FLIP pattern (First, Last, Invert, Play): First: record each item’s current bounding rect. Last: reorder the DOM, then read the new rects. Invert: apply a transform that moves each item back to where it started. Play: remove the transform on the next frame so CSS transitions animate it to place. function flipSort(mode) { const firstRects = new Map(items.map(i => [i, i.getBoundingClientRect()])); applySort(mode); requestAnimationFrame(() => { items.forEach(item => { const first = firstRects.get(item); const last = item.getBoundingClientRect(); const dx = first.left – last.left; const dy = first.top – last.top; item.style.transform = `translate(${dx}px, ${dy}px)`; item.style.transition = ‘none’; requestAnimationFrame(() => { item.style.transform = ”; item.style.transition = ‘transform .4s ease’; }); }); }); } Step 6: Mobile-friendly interactions Phones need a bit of extra care. Here are the tweaks that make a real difference: Make filter buttons at least 44 by 44 pixels to meet touch target guidelines. Allow horizontal scroll on the filter bar with overflow-x: auto and scroll-snap-type: x mandatory. Use loading=”lazy” on images to save bandwidth. Add decoding=”async” so the browser can decode images off the main thread. .filters { display: flex; gap: 8px; overflow-x: auto; scroll-snap-type: x mandatory; padding-bottom: 8px; } .filter-btn { scroll-snap-align: start; min-height: 44px; } Comparison with common approaches Approach Weight Multi-tag Sort Animation W3Schools portfolio Light Limited No Basic Isotope.js Heavy Yes Yes Advanced This tutorial Zero deps Yes Yes FLIP smooth Bonus: combining filter and sort Because filtering and sorting are separate functions that both operate on the same node list, combining them is a one-liner: function refresh() { applyFilter(currentFilter); applySort(sortSelect.value); } Call refresh() whenever the user changes either control. Accessibility checklist Use real <button> elements for filters, not divs. Add aria-pressed on the active filter button. Provide meaningful alt text on every image. Ensure focus outlines remain visible on keyboard navigation. FAQ Do I need a library like Isotope or MixItUp? No. For most portfolios and product grids, vanilla JavaScript with CSS Grid is enough and ships zero kilobytes of dependencies. mozilla.org has a solid rundown on this. How do I support multiple filters at once? Turn filter buttons into toggles and keep an array of active filters. Then in applyFilter check whether the item’s tags include every selected filter. Can I load images dynamically from an API? Yes. Fetch the JSON, build the figure elements with the same data-tags, data-date and data-title attributes,

Hover effects are one of the fastest ways to make a website feel alive. A subtle color shift, a smooth zoom, or a floating shadow can turn a static page into an interactive experience. The best part? You don’t need JavaScript or heavy libraries to build them. Plain CSS hover effects using :hover, transition, and transform are all you need. In this tutorial, we’ll walk through 10 practical examples you can copy, paste, and tweak for your own projects. Whether you’re building buttons, image galleries, or product cards, you’ll find something here to use right away. What Is a CSS Hover Effect? A hover effect is a visual change that happens when a user moves their mouse pointer over an element. In CSS, this is done with the :hover pseudo-class, which targets an element only while the pointer is on top of it. Here’s the simplest possible example: button:hover { background-color: #2563eb; color: white; } That’s it. When the user hovers over the button, the background and text color change instantly. To make the change smooth instead of abrupt, we add a transition. The 3 Building Blocks You Need to Know :hover – the pseudo-class that triggers styles on mouse over. transition – controls the speed and easing of the change. transform – lets you scale, rotate, translate, or skew elements without affecting layout. Combine these three and you can build almost any hover effect you see on the web. 10 CSS Hover Effects With Code Snippets 1. Smooth Color Fade Button The classic. Great for primary call-to-action buttons. .btn-fade { background: #6366f1; color: #fff; padding: 12px 28px; border: none; border-radius: 6px; cursor: pointer; transition: background 0.3s ease; } .btn-fade:hover { background: #4338ca; } 2. Lift-Up Button With Shadow Adds depth and makes the button feel clickable. .btn-lift { background: #10b981; color: #fff; padding: 12px 28px; border: none; border-radius: 6px; cursor: pointer; transition: transform 0.25s ease, box-shadow 0.25s ease; } .btn-lift:hover { transform: translateY(-3px); box-shadow: 0 10px 20px rgba(0,0,0,0.15); } 3. Border Slide-In Button A minimalist effect where a border animates in from one side. Source: https://w3schools.com. .btn-border { position: relative; background: transparent; color: #111; padding: 12px 28px; border: 2px solid #111; overflow: hidden; cursor: pointer; z-index: 1; } .btn-border::before { content: “”; position: absolute; top: 0; left: -100%; width: 100%; height: 100%; background: #111; transition: left 0.3s ease; z-index: -1; } .btn-border:hover { color: #fff; } .btn-border:hover::before { left: 0; } 4. Gradient Shift Button A modern effect using a background gradient that moves on hover. .btn-gradient { background: linear-gradient(90deg, #f472b6, #8b5cf6, #f472b6); background-size: 200% 100%; background-position: 0% 0%; color: #fff; padding: 12px 28px; border: none; border-radius: 30px; cursor: pointer; transition: background-position 0.5s ease; } .btn-gradient:hover { background-position: 100% 0%; } 5. Image Zoom Effect Ideal for galleries, portfolios, and product thumbnails. .img-zoom { overflow: hidden; border-radius: 8px; } .img-zoom img { display: block; width: 100%; transition: transform 0.5s ease; } .img-zoom:hover img { transform: scale(1.1); } Important: the overflow: hidden on the parent is what stops the image from spilling out when it scales. 6. Image Grayscale to Color Great for team member photos or partner logos. .img-gray { filter: grayscale(100%); transition: filter 0.4s ease; } .img-gray:hover { filter: grayscale(0%); } 7. Image Overlay With Text Reveal A caption slides in over the image on hover. .img-overlay { position: relative; overflow: hidden; border-radius: 8px; } .img-overlay img { display: block; width: 100%; } .img-overlay .caption { position: absolute; inset: 0; background: rgba(0,0,0,0.6); color: #fff; display: flex; align-items: center; justify-content: center; opacity: 0; transition: opacity 0.35s ease; } .img-overlay:hover .caption { opacity: 1; } 8. Card Tilt Effect A subtle 3D tilt gives cards a playful feel. .card-tilt { background: #fff; padding: 24px; border-radius: 12px; box-shadow: 0 4px 12px rgba(0,0,0,0.08); transition: transform 0.4s ease, box-shadow 0.4s ease; } .card-tilt:hover { transform: perspective(600px) rotateX(4deg) rotateY(-4deg) translateY(-4px); box-shadow: 0 20px 40px rgba(0,0,0,0.12); } 9. Underline Grow Link A clean alternative to the default underline on text links. .link-grow { position: relative; color: #111; text-decoration: none; } .link-grow::after { content: “”; position: absolute; left: 0; bottom: -3px; width: 100%; height: 2px; background: currentColor; transform: scaleX(0); transform-origin: right; transition: transform 0.3s ease; } .link-grow:hover::after { transform: scaleX(1); transform-origin: left; } 10. Glowing Neon Button Perfect for dark backgrounds and gaming or tech themes. .btn-neon { background: transparent; color: #22d3ee; padding: 12px 28px; border: 2px solid #22d3ee; border-radius: 6px; cursor: pointer; transition: box-shadow 0.3s ease, color 0.3s ease, background 0.3s ease; } .btn-neon:hover { background: #22d3ee; color: #0f172a; box-shadow: 0 0 8px #22d3ee, 0 0 20px #22d3ee, 0 0 40px #22d3ee; } Understanding the Transition Property The transition shorthand takes four values in this order: Value Purpose Example property Which CSS property to animate background, transform, all duration How long the animation lasts 0.3s, 500ms timing-function The easing curve ease, linear, ease-in-out delay Wait time before starting 0s, 200ms For most hover effects, a duration between 0.2s and 0.4s with ease or ease-out feels natural. Anything longer than 0.5s starts to feel sluggish. Best Practices for Hover Effects Always add a transition. Instant style changes feel jarring. Animate transform and opacity, not width or height. These properties are GPU-accelerated and much smoother. Keep durations short. Users hover fast, so keep effects snappy. Provide a focus state too. Add :focus-visible alongside :hover so keyboard users get the same feedback. Respect reduced motion. Wrap large animations in a media query for accessibility: @media (prefers-reduced-motion: reduce) { * { transition: none !important; animation: none !important; } } Mobile Considerations Touch devices don’t have a real hover state. When a user taps an element on mobile, the hover style may stick until they tap elsewhere. To avoid this, you can use the hover media feature: @media (hover: hover) { .btn-lift:hover { transform: translateY(-3px); } } This ensures hover styles only apply on devices that actually support hovering. FAQ Can I use CSS hover effects on any HTML element? Yes. The :hover pseudo-class works on virtually all elements, not just links and buttons. You can apply it to

A well-placed countdown timer can boost conversions on product launch pages, add urgency to promotional offers, and keep event attendees engaged. The good news? You don’t need a plugin or a third-party library to build one. With a bit of HTML, CSS, and vanilla JavaScript, you can ship a clean, brand-matching timer in under 15 minutes. In this tutorial, we’ll walk through building a fully functional countdown timer in JavaScript from scratch, then cover styling tips, edge cases, and optimization strategies that most tutorials skip. What You’ll Build By the end of this guide, you’ll have a responsive countdown timer that: There’s a fuller breakdown if you want the detail. Displays days, hours, minutes, and seconds Updates in real time every second Shows a custom message when the timer hits zero Handles timezone consistency Is fully customizable to match any brand Step 1: The HTML Structure Start with a simple, semantic structure. Each unit of time gets its own container so we can style them independently. <div class=”countdown” id=”countdown”> <div class=”unit”> <span class=”number” id=”days”>00</span> <span class=”label”>Days</span> </div> <div class=”unit”> <span class=”number” id=”hours”>00</span> <span class=”label”>Hours</span> </div> <div class=”unit”> <span class=”number” id=”minutes”>00</span> <span class=”label”>Minutes</span> </div> <div class=”unit”> <span class=”number” id=”seconds”>00</span> <span class=”label”>Seconds</span> </div> </div> <p class=”message” id=”message”></p> Step 2: Style It With CSS Here’s a clean, modern base you can easily adapt. Change the colors, radius, and font to align with your brand identity. .countdown { display: flex; gap: 1rem; justify-content: center; font-family: ‘Inter’, sans-serif; } .unit { background: #111; color: #fff; padding: 1.5rem 1.25rem; border-radius: 12px; min-width: 90px; text-align: center; box-shadow: 0 4px 12px rgba(0,0,0,0.1); } .number { display: block; font-size: 2.5rem; font-weight: 700; line-height: 1; } .label { display: block; font-size: 0.75rem; text-transform: uppercase; letter-spacing: 0.1em; margin-top: 0.5rem; opacity: 0.7; } .message { text-align: center; font-size: 1.25rem; font-weight: 600; margin-top: 1rem; } Step 3: The JavaScript Logic This is where the magic happens. We calculate the difference between the target date and the current time, then break it down into days, hours, minutes, and seconds. // Set your target date (ISO format recommended) const targetDate = new Date(‘2026-12-31T23:59:59’).getTime(); const daysEl = document.getElementById(‘days’); const hoursEl = document.getElementById(‘hours’); const minutesEl = document.getElementById(‘minutes’); const secondsEl = document.getElementById(‘seconds’); const messageEl = document.getElementById(‘message’); const countdownEl = document.getElementById(‘countdown’); function pad(num) { return String(num).padStart(2, ‘0’); } function updateCountdown() { const now = new Date().getTime(); const distance = targetDate – now; if (distance < 0) { clearInterval(timer); countdownEl.style.display = ‘none’; messageEl.textContent = “We’re live!”; return; } const days = Math.floor(distance / (1000 * 60 * 60 * 24)); const hours = Math.floor((distance % (1000 * 60 * 60 * 24)) / (1000 * 60 * 60)); const minutes = Math.floor((distance % (1000 * 60 * 60)) / (1000 * 60)); const seconds = Math.floor((distance % (1000 * 60)) / 1000); daysEl.textContent = pad(days); hoursEl.textContent = pad(hours); minutesEl.textContent = pad(minutes); secondsEl.textContent = pad(seconds); } updateCountdown(); const timer = setInterval(updateCountdown, 1000); That’s the entire timer. Under 30 lines of readable code, no dependencies, no bloat. How the Code Works Target date: We convert the end date to a Unix timestamp using getTime(). Distance calculation: Subtracting the current time from the target gives us milliseconds remaining. Time unit extraction: Using modulo and division, we split milliseconds into days, hours, minutes, and seconds. Padding: The pad() helper ensures single digits show as “05” instead of “5” for a cleaner look. Interval: setInterval re-runs the update every second. When the timer expires, we clear the interval to save resources. Common Pitfalls and How to Fix Them Pitfall Solution Timer shows wrong time for users in other timezones Use UTC or ISO date strings with timezone offset (e.g., 2026-12-31T23:59:59Z) Timer drifts when tab is inactive Recalculate from the target date each tick instead of decrementing counters Flicker on first load Call updateCountdown() once immediately, before starting the interval Memory leak on SPA navigation Always call clearInterval() when the component unmounts Making It Match Your Brand The base timer is intentionally minimal so you can adapt it. Here are quick brand-matching tweaks: Rounded pill style: Change border-radius to 999px and adjust padding. Gradient backgrounds: Replace background: #111 with linear-gradient(135deg, #667eea, #764ba2). Flip animation: Add a CSS keyframe on number change to create a mechanical flip effect. Custom typography: Load your brand’s display font via @font-face or Google Fonts. Compact mode: Hide days and only show hours/minutes/seconds for flash sales under 24 hours. Use Cases Where This Timer Shines Product Launches Place the timer above the fold on your landing page. Combine it with an email capture form so visitors get notified the second the product goes live. Limited-Time Promotions Flash sales convert better with visible urgency. A timer that counts down to the end of a discount period consistently outperforms static “sale ends soon” banners. Event Registration Pages Webinars, conferences, and product demos benefit from a persistent countdown that tells attendees exactly when the event starts. Coming Soon Pages Building hype before a launch? A full-screen countdown paired with an email signup can gather leads long before you have a finished product. There’s a good explainer over at w3schools.com. Bonus: A Reusable Countdown Function If you need multiple timers on the same page, wrap the logic in a reusable factory function: function createCountdown(selector, targetDateStr) { const root = document.querySelector(selector); const target = new Date(targetDateStr).getTime(); const tick = () => { const distance = target – Date.now(); if (distance < 0) { root.innerHTML = ‘<strong>Time is up!</strong>’; clearInterval(id); return; } const d = Math.floor(distance / 86400000); const h = Math.floor((distance % 86400000) / 3600000); const m = Math.floor((distance % 3600000) / 60000); const s = Math.floor((distance % 60000) / 1000); root.textContent = `${d}d ${h}h ${m}m ${s}s`; }; tick(); const id = setInterval(tick, 1000); return () => clearInterval(id); } // Usage: createCountdown(‘#launch-timer’, ‘2026-09-01T10:00:00Z’); Performance Tips Use requestAnimationFrame instead of setInterval only if you need sub-second precision. For standard countdowns, setInterval is more than enough and easier on the CPU. Avoid updating the DOM if the value hasn’t changed. Cache the previous seconds value and skip the

Live chat is one of the fastest ways to turn visitors into customers, but most chat widgets ship 200KB to 500KB of JavaScript that fires on every page load. That is a direct hit to your Largest Contentful Paint, Interaction to Next Paint and overall Core Web Vitals scores. In this guide, we compare three lightweight live chat solutions (Tawk.to, Crisp and Tidio) and show you exactly how to add live chat to a website using lazy loading, so your visitors get the feature without the performance penalty. Why the default install method hurts your website Most vendors give you a copy-paste snippet that loads their SDK synchronously in the <head>. Even with async, the browser still has to parse, compile and execute a large bundle before the widget shows up. On mobile 4G connections, this can add 1 to 3 seconds to your Time to Interactive. sinch.com has a solid rundown on this. The good news: nobody clicks a chat bubble in the first 100 milliseconds of a page load. That means we can safely defer loading until the user actually needs it. Comparing lightweight live chat tools Here is a practical comparison of the three most efficient options in 2026: Feature Tawk.to Crisp Tidio Free plan Yes, unlimited agents Yes, 2 seats Yes, limited chats Widget size (gzipped) ~90KB ~110KB ~180KB AI chatbot included Paid add-on Paid plan Yes, Lyro AI Self-hosted option No No No Best for Budget teams, agencies SaaS, developer-friendly E-commerce, Shopify Our take Tawk.to is the lightest and fully free, best if you just need a chat channel. Crisp has the cleanest API and a modern SDK, ideal for SaaS products. Tidio shines on e-commerce with built-in AI, but ships the heaviest bundle so lazy loading is a must. The lazy-loading strategy Instead of loading the vendor script on page load, we replace the chat widget with a lightweight placeholder button (about 2KB of HTML and CSS). The real script only loads when: The user hovers or clicks the placeholder button, or The browser goes idle after the page has fully loaded, or The user scrolls past a certain threshold. This gives you the best of both worlds: zero impact on initial load and a chat widget that appears instantly when needed. Step 1: Create a fake chat button <button id=”chat-launcher” aria-label=”Open chat”> <svg width=”24″ height=”24″ viewBox=”0 0 24 24″ fill=”white”> <path d=”M20 2H4c-1.1 0-2 .9-2 2v18l4-4h14c1.1 0 2-.9 2-2V4c0-1.1-.9-2-2-2z”/> </svg> </button> <style> #chat-launcher { position: fixed; bottom: 20px; right: 20px; width: 60px; height: 60px; border-radius: 50%; background: #0084ff; border: none; cursor: pointer; box-shadow: 0 4px 12px rgba(0,0,0,0.15); z-index: 9999; } </style> Step 2: Lazy-load Tawk.to on interaction <script> (function() { var loaded = false; function loadTawk() { if (loaded) return; loaded = true; document.getElementById(‘chat-launcher’).style.display = ‘none’; var s = document.createElement(‘script’); s.async = true; s.src = ‘https://embed.tawk.to/YOUR_PROPERTY_ID/default’; s.charset = ‘UTF-8’; s.setAttribute(‘crossorigin’, ‘*’); document.head.appendChild(s); s.onload = function() { if (window.Tawk_API && window.Tawk_API.maximize) { window.Tawk_API.maximize(); } }; } var btn = document.getElementById(‘chat-launcher’); btn.addEventListener(‘mouseenter’, loadTawk, { once: true }); btn.addEventListener(‘click’, loadTawk, { once: true }); // Fallback: load when browser is idle if (‘requestIdleCallback’ in window) { requestIdleCallback(loadTawk, { timeout: 8000 }); } else { setTimeout(loadTawk, 6000); } })(); </script> Step 3: The same pattern for Crisp <script> function loadCrisp() { window.$crisp = []; window.CRISP_WEBSITE_ID = “YOUR_WEBSITE_ID”; var d = document, s = d.createElement(“script”); s.src = “https://client.crisp.chat/l.js”; s.async = 1; d.getElementsByTagName(“head”)[0].appendChild(s); } document.getElementById(‘chat-launcher’) .addEventListener(‘click’, loadCrisp, { once: true }); </script> Step 4: The same pattern for Tidio <script> function loadTidio() { var s = document.createElement(‘script’); s.src = ‘//code.tidio.co/YOUR_PUBLIC_KEY.js’; s.async = true; document.body.appendChild(s); } document.getElementById(‘chat-launcher’) .addEventListener(‘click’, loadTidio, { once: true }); </script> Measuring the impact Before and after our lazy-loading approach on a real client site running Tidio: This guide goes deeper on it. Metric Default install Lazy-loaded LCP 3.4s 1.8s Total Blocking Time 640ms 90ms JS transferred on load 312KB 2KB PageSpeed score (mobile) 62 94 Extra performance tips Add <link rel=”preconnect” href=”https://embed.tawk.to”> so the DNS handshake is ready when the user clicks. Never load chat on transactional pages like checkout unless it is critical for conversion. Skip loading the widget for bots by checking navigator.userAgent. This keeps Lighthouse audits clean. If you use a consent banner, gate the chat loader behind user consent to stay GDPR-compliant. FAQ Does lazy loading hurt chat conversion rates? No. In our tests, conversion actually improved because pages load faster, bounce rates drop, and the chat button still appears instantly thanks to the CSS placeholder. Which live chat is best for a small business in 2026? If budget is your priority, Tawk.to remains unbeatable with unlimited free agents. For a modern feel and better developer tools, Crisp is worth its price. For online stores, Tidio with Lyro AI handles most tier-1 questions automatically. Can I use this method with WordPress? Yes. Paste the placeholder button and lazy-loading script into your theme footer or use a plugin like WPCode to inject it. Avoid using the official Tawk.to or Tidio plugins, which load the script immediately. Will Google penalize me for loading third-party scripts? Google does not penalize scripts directly, but Core Web Vitals affect ranking. A heavy synchronous chat widget can push your LCP and INP into the red. Lazy loading solves this cleanly. Should I use a self-hosted open-source chat instead? Solutions like Chatwoot or Papercups are great if you have DevOps resources. For most teams, a lazy-loaded SaaS widget delivers 95% of the value with none of the maintenance. There’s a fuller breakdown if you want the detail. Wrapping up Adding live chat to your website should not cost you a full second of load time. By deferring the vendor SDK behind a lightweight placeholder and loading it on interaction or during idle time, you keep your Core Web Vitals green while still giving customers a fast way to reach you. Pick the tool that matches your use case, drop in the snippet above, and measure the difference in your next Lighthouse audit.

A favicon is that tiny icon displayed in your browser tab, bookmarks bar and search results next to your site name. It’s a small detail, but it plays a big role in branding, trust and recognition. In this practical guide, we’ll walk you through three proven methods to add a favicon to WordPress, cover the correct sizes and formats, and show you how to verify everything works properly. What Is a Favicon and Why Does It Matter? A favicon (short for “favorite icon”) is a small square image that represents your website across browsers and devices. In WordPress, it’s officially called a Site Icon. A well-designed favicon helps visitors: Identify your site among dozens of open tabs Recognize your brand in bookmarks and history Trust your website as a professional entity Favicon Requirements: Size and Format Before uploading your favicon, make sure it meets WordPress requirements. Here’s a quick reference table: Attribute Recommended Value Minimum Size 512 x 512 pixels Shape Square (1:1 ratio) Accepted Formats .png, .jpg, .ico, .gif Best Format PNG (transparent background) Max File Size Under 100 KB Tip: If you don’t have a favicon yet, you can create one using a free tool like Favicon.io, Canva, or RealFaviconGenerator. Method 1: Add a Favicon via the WordPress Customizer (Easiest) This is the native WordPress method and works with almost every theme. No code, no plugins. Log in to your WordPress admin dashboard. Go to Appearance > Customize. Click on Site Identity. Scroll down to the Site Icon section. Click Select site icon and upload your image (or choose one from the Media Library). Crop the image if prompted, then click Publish to save your changes. If you’re using a block theme (WordPress 6.0 and above), the path may be slightly different: Go to Appearance > Editor Select Styles or Settings > Site Identity Click Site Icon and upload Method 2: Add a Favicon Manually Through Theme Files Want full control? You can add the favicon directly to your theme’s header.php file. This method is ideal for developers or for adding multiple icon variants (Apple Touch Icon, Android Chrome icon, etc.). Step 1: Upload Your Favicon Files Using FTP or your hosting file manager, upload your favicon files (for example favicon.ico, apple-touch-icon.png) to your theme’s root folder: /wp-content/themes/your-theme/ Step 2: Edit header.php Open header.php and add the following lines inside the <head> tag: <link rel=”icon” type=”image/png” href=”<?php echo get_stylesheet_directory_uri(); ?>/favicon.png”> <link rel=”apple-touch-icon” href=”<?php echo get_stylesheet_directory_uri(); ?>/apple-touch-icon.png”> <link rel=”shortcut icon” href=”<?php echo get_stylesheet_directory_uri(); ?>/favicon.ico”> Important: Always use a child theme when editing theme files. Otherwise, your changes will be lost the next time your theme updates. Step 3: Save and Clear Cache Save the file, clear any caching plugins, and refresh your site. Method 3: Add a Favicon Using a Plugin If you’re not comfortable editing files and want more control than the Customizer offers, a plugin is a great middle-ground option. Recommended Plugins RealFaviconGenerator – generates all icon variants for every device Heroic Favicon Generator – simple and beginner-friendly Favicon by RealFaviconGenerator – popular and well maintained Installation Steps Go to Plugins > Add New. Search for your favorite favicon plugin. Click Install Now, then Activate. Navigate to Appearance > Favicon (or the plugin’s settings page). Upload your master image (at least 512×512 px). Customize the appearance for iOS, Android, Windows and macOS. Click Generate favicon and let the plugin handle the rest. How to Verify Your Favicon Is Working Once your favicon is added, you’ll want to make sure it appears correctly: Open your site in an incognito window to bypass browser cache. Check the browser tab. Your icon should appear next to the page title. Bookmark the page and verify the icon shows in your bookmarks bar. Test on multiple browsers: Chrome, Firefox, Safari, Edge. Check on mobile by adding your site to the home screen. Use realfavicongenerator.net/favicon_checker for a full audit. Common Issues and Fixes Favicon Not Showing Up? Clear your browser cache – old icons are often cached for days. Clear your WordPress cache (WP Rocket, W3 Total Cache, etc.). Check the file path – make sure the URL to the favicon is correct. Test in incognito mode to bypass all cache layers. Confirm the file exists by visiting yourdomain.com/favicon.ico directly. Favicon Not Updating? This is almost always a cache issue. Force a refresh by adding a version parameter to your favicon URL, for example: favicon.png?v=2 Which Method Should You Choose? Method Best For Difficulty Customizer Most users, quick setup Easy Theme Files Developers, custom setups Advanced Plugin Multi-device optimization Easy FAQ Why is my favicon not showing up in WordPress? The most common reason is browser or plugin caching. Clear your cache, test in incognito mode, and make sure the favicon file actually exists at the expected URL. Where is the favicon in WordPress? WordPress calls it the Site Icon. You’ll find it under Appearance > Customize > Site Identity, or in the block-based Editor under Styles > Site Identity. How do I insert a favicon? Upload a square image (at least 512×512 px) to the Site Icon section of the WordPress Customizer, or add it manually via header.php, or use a dedicated plugin. How do I add a favicon in WooCommerce? WooCommerce uses the same favicon as your WordPress installation. Simply set your Site Icon via Appearance > Customize > Site Identity and it will appear across all WooCommerce pages. What is the ideal favicon size for WordPress? WordPress requires a minimum of 512 x 512 pixels and will automatically generate smaller versions (16×16, 32×32, 180×180) for different devices. Can I change the favicon without a plugin? Yes. The WordPress Customizer allows you to change the Site Icon without any plugin or code. It’s the recommended method for most users. Conclusion Adding a favicon to WordPress is a small task with a big visual impact. Whether you prefer the built-in Customizer, hands-on theme file editing, or the flexibility of a plugin, you now have three reliable methods to choose from. Pick

A well-crafted back to top button is one of those tiny UX details that can dramatically improve navigation on long pages, blogs, documentation sites, and product listings. In this tutorial, we will build a lightweight, accessible, and smooth-scrolling back to top button using nothing more than plain HTML, CSS, and a few lines of JavaScript. No libraries, no bloat. By the end of this guide, you will have a production-ready snippet you can drop into any project, including Express.js views, static sites, WordPress themes, or single-page applications. What Is a Back to Top Button? A back to top button is a small floating control, typically anchored to the bottom-right corner of the viewport, that scrolls the user back to the top of the page when clicked. It usually appears only after the user has scrolled down a certain distance, keeping the interface clean when it is not needed. When Should You Use One? Long-form content such as blog posts, guides, and documentation Infinite scroll or lazy-loaded feeds Product listing pages with heavy filtering Mobile layouts where scrolling up manually is tedious If your page fits in one or two viewport heights, you probably do not need one. Reserve it for pages taller than roughly four screens. Step 1: Add the HTML We will use a real <button> element rather than a <div> or <a>. This matters for accessibility and keyboard navigation. <button id=”backToTop” class=”back-to-top” aria-label=”Scroll back to top” title=”Back to top”> <svg xmlns=”http://www.w3.org/2000/svg” width=”24″ height=”24″ viewBox=”0 0 24 24″ fill=”none” stroke=”currentColor” stroke-width=”2″ stroke-linecap=”round” stroke-linejoin=”round” aria-hidden=”true”> <path d=”M18 15l-6-6-6 6″/> </svg> </button> Place this markup right before your closing </body> tag so it stays out of the main document flow. Step 2: Style It With CSS The CSS handles positioning, appearance, and the smooth fade transition when the button appears or disappears. .back-to-top { position: fixed; bottom: 2rem; right: 2rem; width: 48px; height: 48px; border: none; border-radius: 50%; background-color: #0d6efd; color: #ffffff; display: flex; align-items: center; justify-content: center; cursor: pointer; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); opacity: 0; visibility: hidden; transform: translateY(10px); transition: opacity 0.3s ease, transform 0.3s ease, visibility 0.3s; z-index: 999; } .back-to-top.is-visible { opacity: 1; visibility: visible; transform: translateY(0); } .back-to-top:hover, .back-to-top:focus-visible { background-color: #0b5ed7; outline: 2px solid #ffffff; outline-offset: 2px; } @media (prefers-reduced-motion: reduce) { .back-to-top { transition: opacity 0.2s ease; transform: none; } } Key CSS Choices Explained position: fixed keeps the button anchored while the user scrolls opacity + visibility creates a smooth fade without leaving an invisible click target focus-visible ensures keyboard users see a clear focus ring prefers-reduced-motion respects users who disable animations Step 3: Add the JavaScript We only need a small script to toggle the visible class and handle the scroll action. (function () { const button = document.getElementById(‘backToTop’); if (!button) return; const SCROLL_THRESHOLD = 300; // pixels let ticking = false; function updateButton() { if (window.scrollY > SCROLL_THRESHOLD) { button.classList.add(‘is-visible’); } else { button.classList.remove(‘is-visible’); } ticking = false; } window.addEventListener(‘scroll’, function () { if (!ticking) { window.requestAnimationFrame(updateButton); ticking = true; } }, { passive: true }); button.addEventListener(‘click’, function () { const prefersReducedMotion = window.matchMedia(‘(prefers-reduced-motion: reduce)’).matches; window.scrollTo({ top: 0, behavior: prefersReducedMotion ? ‘auto’ : ‘smooth’ }); }); })(); Why This Script Is Fast Uses requestAnimationFrame to throttle scroll events Uses a passive scroll listener so the browser can optimize scrolling performance Falls back to instant scroll when the user prefers reduced motion Wrapped in an IIFE to avoid polluting the global scope Accessibility Checklist A back to top button should be usable by everyone, not just mouse users. Here is what to verify before shipping: Concern Implementation Keyboard focus Use a native <button> element Screen readers Add aria-label=”Scroll back to top” Motion sensitivity Respect prefers-reduced-motion Focus after scroll Optionally move focus to the main heading Contrast Maintain at least 4.5:1 ratio for the icon Optional: Move Focus After Scrolling For screen reader users, scrolling visually to the top does not move the focus. You can improve this by focusing your main landmark after the scroll completes: button.addEventListener(‘click’, function () { window.scrollTo({ top: 0, behavior: ‘smooth’ }); const main = document.querySelector(‘main, h1’); if (main) { main.setAttribute(‘tabindex’, ‘-1’); main.focus({ preventScroll: true }); } }); Design Best Practices in 2026 Show it only when useful. Reveal after the user scrolls at least 300 to 500 pixels. Keep it small. Around 40 to 56 pixels wide, never dominating the viewport. Use a clear icon. An upward-pointing chevron or arrow is universally understood. Do not block content. On mobile, avoid overlapping call-to-action buttons or chat widgets. Match your brand. Use your primary color, but ensure contrast against varied backgrounds. Common Mistakes to Avoid Using an <a href=”#top”> without preventDefault, which pushes an entry into browser history Animating scroll with heavy JavaScript loops when window.scrollTo handles it natively Forgetting to test with keyboard-only navigation Placing the button over important interactive UI on small screens FAQ Do I need JavaScript for a back to top button? Not necessarily. A pure anchor link pointing to #top combined with scroll-behavior: smooth on the html element works without any JavaScript. However, JavaScript gives you control over when the button appears and how it behaves on reduced-motion systems. What is the ideal scroll distance before showing the button? Between 300 and 500 pixels works well for most sites. On very long articles, you might delay it further to avoid distraction during the first fold of reading. Is a back to top button good for SEO? Indirectly, yes. It improves dwell time and reduces friction on long pages, which can positively impact engagement metrics. It has no direct ranking factor, but better UX typically correlates with better rankings. Should the button appear on mobile? Yes, especially on mobile, where scrolling long articles is tedious. Just be careful not to cover sticky navigation bars, floating chat icons, or cookie banners. Can I use CSS scroll-behavior instead of JavaScript? Absolutely. Add html { scroll-behavior: smooth; } and link to an anchor at the top of the page. The trade-off is that you

You’ve seen it on Medium, on major blogs, on documentation sites: a thin colored bar at the top of the page that fills up as you scroll down an article. It’s small, it’s subtle, and it dramatically improves the reading experience. In this tutorial, we’ll build a reading progress bar with CSS and vanilla JavaScript that you can drop into any blog, WordPress site, or custom project in under 5 minutes. No frameworks. No libraries. Just clean code you can copy, paste, and style however you like. What Is a Reading Progress Bar? A reading progress bar is a visual indicator, usually fixed at the top of the viewport, that reflects how far a user has scrolled through the main content of a page. It answers a simple but powerful question for your readers: how much is left to read? Benefits of adding one to your blog: Reduces bounce rate on long-form articles Sets clear expectations about article length Provides a subtle, modern UX touch Encourages users to keep scrolling Two Approaches: CSS-Only vs. JavaScript Before jumping into code, let’s compare the two main approaches so you can choose the right one for your project. Feature CSS-Only (animation-timeline) JavaScript Browser support Modern browsers only Universal Performance Excellent (native) Very good with throttling Flexibility Limited Full control Track only article content Yes Yes We’ll cover both. Start with the JavaScript version if you need broad support, or jump to the CSS-only version if you’re targeting modern browsers. Step 1: Add the HTML Markup The bar itself is just an empty div placed near the top of your body. Add this snippet right after your opening <body> tag: <div id=”reading-progress”></div> That’s it. The div will be styled and updated dynamically. Step 2: Style the Bar With CSS Here is the base CSS. It fixes the bar at the top, gives it height, and prepares the fill state: #reading-progress { position: fixed; top: 0; left: 0; height: 4px; width: 0%; background: linear-gradient(90deg, #ff6b6b, #f06595); z-index: 9999; transition: width 0.1s ease-out; } @media (max-width: 600px) { #reading-progress { height: 3px; } } Key styling choices explained: position: fixed keeps the bar visible while scrolling z-index: 9999 ensures it stays above sticky headers and modals transition smooths out the fill animation Media query reduces height on mobile for a lighter feel Step 3: The JavaScript Logic This is where the magic happens. Add this script before the closing </body> tag: <script> (function() { const bar = document.getElementById(‘reading-progress’); const article = document.querySelector(‘article’) || document.body; function updateProgress() { const rect = article.getBoundingClientRect(); const total = rect.height – window.innerHeight; const scrolled = -rect.top; const percent = Math.min(Math.max((scrolled / total) * 100, 0), 100); bar.style.width = percent + ‘%’; } let ticking = false; window.addEventListener(‘scroll’, function() { if (!ticking) { window.requestAnimationFrame(function() { updateProgress(); ticking = false; }); ticking = true; } }); updateProgress(); })(); </script> What the script does: Selects the progress bar and the article container Calculates the total scrollable distance within the article Determines how much of that distance has been scrolled Updates the bar width using requestAnimationFrame for smooth performance Note: the script targets the <article> element. This means the bar only fills while the user is inside the article, not while scrolling past headers or footers. If your theme doesn’t use an <article> tag, replace the selector with your content wrapper class, for example .entry-content or .post-content. Step 4: The CSS-Only Alternative If you only need to support modern browsers, you can skip JavaScript entirely using animation-timeline: scroll(). Here is the complete snippet: #reading-progress { position: fixed; top: 0; left: 0; height: 4px; width: 100%; background: linear-gradient(90deg, #ff6b6b, #f06595); transform-origin: 0 50%; animation: progress linear; animation-timeline: scroll(root); z-index: 9999; } @keyframes progress { from { transform: scaleX(0); } to { transform: scaleX(1); } } This uses the scroll-driven animations feature, which is supported in Chrome, Edge, and Opera. Firefox and Safari support is progressing, so treat this as progressive enhancement. How to Add It to WordPress There are three easy ways to integrate the code into a WordPress site. Option 1: Via a Child Theme Add the CSS to your child theme’s style.css Add the JavaScript to a new file called progress.js in your child theme Enqueue both in functions.php using wp_enqueue_style and wp_enqueue_script Insert the <div id=”reading-progress”></div> in your header.php Option 2: Using a Code Snippet Plugin Plugins like WPCode or Code Snippets let you inject the HTML div, CSS, and JS without editing theme files. Set the snippet to run only on single blog posts using their conditional logic. Option 3: Directly in the Block Editor Use a Custom HTML block at the top of your post template to insert the markup, then add the CSS via Appearance > Customize > Additional CSS. Mobile Behavior and Best Practices Mobile users represent the majority of blog traffic, so the bar should feel native on small screens. A few tips: Keep it thin. 3px is enough on mobile. Anything taller competes with your content. Avoid distracting animations. A simple width transition of 0.1s is enough. Respect reduced motion. Wrap animations in a @media (prefers-reduced-motion: no-preference) query. Test with sticky headers. If your header is sticky, make sure the bar sits above it or just below it, not overlapping the logo. Use accessible colors. The bar should have sufficient contrast against your header background. Styling Variations The base version uses a gradient, but you can go creative: Solid brand color for a minimal look Animated shimmer using a repeating linear gradient Bottom placement by changing top: 0 to bottom: 0 Vertical bar on the right edge, useful for documentation sites Debugging Common Issues Problem Likely Cause Bar doesn’t move Selector doesn’t match your content container Bar fills too early Article element is shorter than the viewport Bar hidden behind header Header has higher z-index than 9999 Choppy animation Scroll handler is not throttled with requestAnimationFrame FAQ Does a reading progress bar affect page speed? No. The script is a few lines and uses requestAnimationFrame, which

If you run a WordPress blog, you already know the drill: every long-form article needs a table of contents to help readers navigate, improve dwell time, and pick up those juicy sitelinks in Google search results. The lazy solution is to install a plugin. The smart solution is to build it yourself. In this tutorial, we will show you how to add a table of contents in WordPress without a plugin by parsing your H2 and H3 headings automatically with a few lines of PHP and a sprinkle of JavaScript. No bloat, no third-party scripts, no performance hit. Why Build a Table of Contents Without a Plugin? Most tutorials on the first page of Google will tell you to manually create anchor tags and lists for every post. That works, but it is tedious and error-prone. Others will push you toward heavy plugins like Easy Table of Contents. Here is why the DIY approach wins in 2026: Performance: No extra HTTP requests, no jQuery dependency, no admin bloat. Full control: You decide the markup, the styling, and the behavior. SEO friendly: Clean semantic HTML with proper anchor links helps Google generate jump-to links in the SERP. No plugin conflicts: One less thing to update or break during a core WordPress upgrade. Reusable: Once written, it works on every post automatically. How It Works: The Logic Behind Automatic TOC Generation The idea is simple. Before WordPress prints your post content on the page, we intercept it with a filter, scan it for H2 and H3 tags, inject unique IDs into those headings, and build a nested list of links. Then we prepend that list to the content. Here is a quick overview of the pieces involved: Component Role PHP function in functions.php Parses headings, injects IDs, generates the TOC list WordPress filter the_content Applies the function to every single post CSS in your theme stylesheet Styles the TOC box Vanilla JavaScript (optional) Adds smooth scroll and collapse behavior Step 1: Add the PHP Function to Your Theme Open the functions.php file of your child theme (never edit the parent theme directly). Paste the following code at the bottom: function expressjs_generate_toc($content) { if (!is_single() || !in_the_loop() || !is_main_query()) { return $content; } // Match all H2 and H3 tags preg_match_all(‘/<h([2-3])(.*?)>(.*?)<\/h[2-3]>/i’, $content, $matches, PREG_SET_ORDER); if (count($matches) < 3) { return $content; // Skip TOC if fewer than 3 headings } $toc = ‘<div class=”expressjs-toc” id=”toc”>’; $toc .= ‘<p class=”toc-title”>Table of Contents</p>’; $toc .= ‘<ul>’; $current_level = 2; foreach ($matches as $match) { $level = (int) $match[1]; $title = strip_tags($match[3]); $anchor = sanitize_title($title); // Inject the ID into the heading inside the content $new_heading = ‘<h’ . $level . ‘ id=”‘ . $anchor . ‘”‘ . $match[2] . ‘>’ . $match[3] . ‘</h’ . $level . ‘>’; $content = str_replace($match[0], $new_heading, $content); if ($level == 3 && $current_level == 2) { $toc .= ‘<ul>’; $current_level = 3; } elseif ($level == 2 && $current_level == 3) { $toc .= ‘</ul>’; $current_level = 2; } $toc .= ‘<li><a href=”#’ . $anchor . ‘”>’ . $title . ‘</a></li>’; } if ($current_level == 3) { $toc .= ‘</ul>’; } $toc .= ‘</ul></div>’; return $toc . $content; } add_filter(‘the_content’, ‘expressjs_generate_toc’); What this code does, step by step: Runs only on single posts inside the main loop. Uses a regex to grab every H2 and H3 in the post content. Skips generation if the post has fewer than 3 headings (short articles do not need a TOC). Creates a slug for each heading using sanitize_title(). Injects an id attribute into each heading so anchor links work. Builds a nested unordered list and prepends it to the content. Step 2: Style the Table of Contents with CSS Add the following CSS to your theme’s style.css or the WordPress Customizer under Additional CSS: .expressjs-toc { background: #f7f9fc; border-left: 4px solid #0d6efd; padding: 20px 25px; margin: 30px 0; border-radius: 6px; font-size: 15px; } .expressjs-toc .toc-title { font-weight: 700; font-size: 18px; margin: 0 0 12px 0; } .expressjs-toc ul { list-style: none; padding-left: 15px; margin: 0; } .expressjs-toc ul ul { padding-left: 20px; margin-top: 6px; } .expressjs-toc li { margin: 6px 0; } .expressjs-toc a { text-decoration: none; color: #0d6efd; } .expressjs-toc a:hover { text-decoration: underline; } Feel free to adjust the colors to match your brand. This minimal style keeps the TOC readable without shouting for attention. Step 3: Add Smooth Scroll with Vanilla JavaScript Modern browsers support smooth scrolling natively via CSS, but a tiny script gives you more control (like offsetting for a sticky header). Add this to your theme’s JS file or drop it inline before the closing body tag: document.addEventListener(‘DOMContentLoaded’, function() { const links = document.querySelectorAll(‘.expressjs-toc a’); links.forEach(link => { link.addEventListener(‘click’, function(e) { e.preventDefault(); const target = document.querySelector(this.getAttribute(‘href’)); if (target) { const offset = 80; // adjust for sticky header height const top = target.getBoundingClientRect().top + window.pageYOffset – offset; window.scrollTo({ top: top, behavior: ‘smooth’ }); history.pushState(null, null, this.getAttribute(‘href’)); } }); }); }); That is it. Publish a post with a few H2 and H3 tags and reload it. You should see a clean, automatic table of contents at the top. Optional Improvements Make the TOC Collapsible If your posts are long, users may want to hide the TOC. Wrap the list in a details element for a native accordion with zero JavaScript: <details open> <summary>Table of Contents</summary> <ul>…</ul> </details> Add a Floating Sidebar TOC For desktop readers, a sticky TOC on the left side is a huge UX win. Use CSS position: sticky with a top offset and hide it on mobile with a media query. Support H4 Headings Simply update the regex pattern from [2-3] to [2-4] and add another nesting level in the loop. Common Pitfalls to Avoid Do not use it on pages with existing anchor plugins. You will get duplicate IDs. Escape HTML entities inside heading text. If your titles include quotes or ampersands, use esc_html() when building the anchor. Test with caching plugins. Clear your cache after editing functions.php or the TOC

If your WordPress site feels sluggish or PageSpeed Insights keeps flagging the dreaded “Reduce unused CSS” warning, you are not alone. Bloated stylesheets are one of the top reasons WordPress sites fail Core Web Vitals in 2026. The good news? You can fix it, and you don’t need to be a developer to do it. In this guide, we will walk through exactly how to remove unused CSS in WordPress using three complementary approaches: manual auditing with Chrome DevTools, automation with PurgeCSS, and plugin-based solutions. By the end, you will know which method fits your stack and how to recover those lost milliseconds. Why Unused CSS Slows Down WordPress Every WordPress theme and plugin loads its own stylesheet, whether or not the current page actually uses those styles. A contact form plugin loads its CSS on your homepage. A slider library injects its styles on your blog posts. Multiply that across 15 to 30 plugins, and you end up shipping hundreds of kilobytes of CSS that the browser never renders. The consequences are real: Render-blocking resources delay the First Contentful Paint (FCP) Larger CSS payloads hurt Largest Contentful Paint (LCP) Mobile users on 4G connections wait longer for above-the-fold content Google’s ranking signals take a hit, especially after the 2025 Core Web Vitals refinements Step 1: Audit Your Site with Chrome DevTools Coverage Before you remove anything, you need to know what is actually unused. Chrome’s built-in Coverage tool is the fastest way to get that data, and it is free. How to Run the Coverage Report Open your WordPress site in Chrome (use Incognito to disable extensions). Press F12 to open DevTools. Press Ctrl + Shift + P (or Cmd + Shift + P on Mac) and type “Show Coverage”. Click the reload icon in the Coverage panel to record. Filter by CSS in the dropdown. You will see a red and blue bar for each stylesheet showing the percentage of unused bytes. Anything above 60% unused is a strong candidate for optimization. Reading the Results Unused % Action 0 to 30% Leave it alone, the file is doing its job 30 to 60% Consider conditional loading 60 to 100% Prime target for PurgeCSS or removal Step 2: Identify the Culprits (Plugins and Themes) The Coverage report tells you which files are wasteful. Now you need to figure out where those files come from. Right-click the URL in DevTools and check the path: /wp-content/plugins/[plugin-name]/… means a plugin is loading the CSS /wp-content/themes/[theme-name]/… means your theme is responsible External domains usually point to fonts, analytics, or third-party widgets Common offenders we see in 2026 audits include page builders (Elementor, Divi, WPBakery), contact form plugins loading globally, and social sharing libraries. Step 3: Choose Your Removal Strategy There are three viable paths. Most sites end up combining at least two of them. You can read more here. Option A: Plugin-Based Removal (Easiest) If you want results in 15 minutes, a dedicated plugin is the way to go. Here are the leading options as of mid-2026: Plugin Price Best For Perfmatters Paid Automated removal with file or inline mode WP Rocket Paid Full caching plus unused CSS in one tool Debloat Free Advanced users on a budget Asset CleanUp Free / Pro Per-page conditional unloading Pro tip: after enabling “Remove Unused CSS” in any of these, always test 5 to 10 pages manually. Sometimes the regeneration misses styles needed for accordions, tabs, or hover states. Option B: PurgeCSS (For Developers) If you have command line access and a staging environment, PurgeCSS gives you the most surgical control. It scans your HTML and templates, then strips selectors that are never referenced. Basic workflow: Install Node.js and run npm install -g purgecss Export your rendered HTML pages with a crawler like wget Run purgecss –css style.css –content **/*.html –output ./purged/ Replace your theme’s stylesheet with the purged version Test, test, and test again PurgeCSS is powerful but unforgiving. Dynamic classes added by JavaScript can be stripped accidentally. Use the safelist option to protect them. Option C: Conditional Loading (Manual But Free) If a plugin’s CSS only matters on one page, why load it everywhere? Use a small snippet in your theme’s functions.php: add_action(‘wp_enqueue_scripts’, function() { if (!is_page(‘contact’)) { wp_dequeue_style(‘contact-form-7′); } }, 100); This approach is free, lightweight, and surprisingly effective for sites with under 20 plugins. Step 4: Re-Test and Validate After applying your changes, run these checks: PageSpeed Insights on at least 3 different page types (home, post, archive) Chrome Coverage report to confirm unused CSS dropped Visual regression check on mobile and desktop Interaction tests: forms, menus, modals, sliders A successful optimization typically reduces CSS payload by 40 to 80% and shaves 0.5 to 1.5 seconds off LCP. Source: https://stackoverflow.com. Common Pitfalls to Avoid Don’t purge on a live site first. Always use staging. Don’t trust automation blindly. Dynamic content from AJAX often breaks. Don’t forget to clear caches after every change (page cache, CDN, browser). Don’t combine too many optimization plugins. They conflict and double-process CSS. FAQ Can I remove unused CSS in WordPress without a plugin? Yes. You can use Chrome DevTools to identify unused styles, then either dequeue plugin stylesheets via functions.php or run PurgeCSS manually against exported HTML. It takes more effort but costs nothing. Does removing unused CSS really improve SEO? Indirectly, yes. Faster pages improve Core Web Vitals, which are confirmed Google ranking signals. A 1 second LCP improvement often translates to measurable ranking and conversion gains. Is PurgeCSS safe for sites using Elementor or Divi? It can be, but page builders generate many dynamic classes. Use a generous safelist and always validate visually. Plugin-based solutions like Perfmatters or WP Rocket are often safer for builder-heavy sites. How often should I re-run the unused CSS audit? Every time you add a new plugin or major theme update. At minimum, audit your site quarterly to catch creeping bloat. What if WP Rocket’s Remove Unused CSS feature breaks my site? Switch to the “Load CSS asynchronously” fallback