<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[shahreweb]]></title><description><![CDATA[shahreweb]]></description><link>https://shahreweb.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 14:59:25 GMT</lastBuildDate><atom:link href="https://shahreweb.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Four Small WordPress Bugs Our PageSpeed and Search Console Reports Exposed]]></title><description><![CDATA[A soft 404 on /.well-known/, stray /feed/ URLs, a bloated llms.txt and an ARIA list bug on an Elementor loop grid: symptoms, causes and fixes.]]></description><link>https://shahreweb.hashnode.dev/four-small-wordpress-bugs-our-pagespeed-and-search-console-reports-exposed</link><guid isPermaLink="true">https://shahreweb.hashnode.dev/four-small-wordpress-bugs-our-pagespeed-and-search-console-reports-exposed</guid><category><![CDATA[llms.txt]]></category><category><![CDATA[Accessibility]]></category><category><![CDATA[Elementor]]></category><category><![CDATA[SEO]]></category><category><![CDATA[WordPress]]></category><dc:creator><![CDATA[shahreweb]]></dc:creator><pubDate>Sun, 22 Nov 2026 10:57:06 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6b02c74ac8790508fabb6fa7/cebed67e-ceac-4765-ae01-fb79f3687d86.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Some of the most useful problems on a website are the quiet ones. They don't break anything visible, but they show up in audit reports as odd warnings. Here are four we found on our own WordPress and Elementor site, written as short case files.</p>
<h2>Case 1: A failing <code>ai-catalog.json</code> audit</h2>
<p><strong>Symptom.</strong> PageSpeed Insights' Agentic Browsing section reported that the <code>ai-catalog.json</code> audit was invalid, even though we had never created such a file.</p>
<p><strong>Cause.</strong> When we opened <code>/.well-known/ai-catalog.json</code> in a browser, we did not get a 404. We got the homepage. That is a soft 404: the server answered "200 OK" for a URL that does not exist. A catalog check that expects either nothing or valid JSON will fail when it receives an HTML page.</p>
<p><strong>Fix.</strong> The behavior came from a fallback redirect that sent unknown URLs to the homepage. After fixing that, both the catalog URL and a random non-existent URL returned a proper "page not found" response, and the audit changed to "not applicable".</p>
<p><strong>Quick test for your own site:</strong></p>
<pre><code class="language-bash">curl -I https://example.com/this-page-does-not-exist-12345
</code></pre>
<p>You should see a <code>404</code> status. If you see <code>200</code> or a redirect to the homepage, you have a soft 404.</p>
<h2>Case 2: Stray <code>/feed/</code> URLs in Search Console</h2>
<p><strong>Symptom.</strong> The "Crawled – currently not indexed" report listed several URLs ending in <code>/feed/</code>, such as post feeds and tag feeds.</p>
<p><strong>Cause.</strong> WordPress generates an RSS feed for almost everything: posts, categories, tags and comments. They are crawlable, they are not pages you want indexed, and they add noise to your reports.</p>
<p><strong>Fix.</strong> We removed the extra feeds with a small snippet. A simplified version of the idea looks like this:</p>
<pre><code class="language-php">add_action( 'template_redirect', function () {
    if ( is_feed() &amp;&amp; ( is_singular() || is_category() || is_tag() || is_tax() ) ) {
        wp_die( 'This feed is not available.', '', array( 'response' =&gt; 410 ) );
    }
} );
</code></pre>
<p>A <code>410</code> tells crawlers the URL is gone for good. Test it on staging first, and decide deliberately whether you want to keep the main site feed. After deploying, we used "Validate Fix" in Search Console. One thing to double-check: another plugin or snippet may already disable feeds with a different message, so test several feed URLs.</p>
<h2>Case 3: A bloated <code>llms.txt</code></h2>
<p><strong>Symptom.</strong> Our SEO plugin generated an <code>llms.txt</code> file, but it was hard to read: no summary at the top, a homepage entry that contained only the site name, and category and tag entries that dumped their full long descriptions into the file.</p>
<p><strong>Cause.</strong> The plugin pulls descriptions from whatever fields exist. Long taxonomy descriptions written for the web were never meant to be a short entry in a link index.</p>
<p><strong>Fix.</strong> We did four things:</p>
<ol>
<li>Added a short summary at the top.</li>
<li>Stopped listing taxonomies in the default output.</li>
<li>Wrote the homepage and contact entries by hand so they say what each page offers.</li>
<li>Used the "extra content" field for a small manual section: topics, project industries and the work process.</li>
</ol>
<p>A note of honesty: <code>llms.txt</code> is a newer convention, and we are not claiming it improves rankings. A readable file is simply cheaper to maintain and easier for any reader, human or machine, to understand.</p>
<h2>Case 4: "Accessibility tree is not well-formed"</h2>
<p><strong>Symptom.</strong> An accessibility audit failed on two elements.</p>
<p><strong>Cause.</strong></p>
<ol>
<li>An Elementor Loop Grid container had <code>role="list"</code>, but its children did not have <code>role="listitem"</code>, so the list was invalid.</li>
<li>An icon-only link that opens a popup had no accessible name.</li>
</ol>
<p><strong>Fix.</strong> For the first, we had two options: remove the role, or complete the structure. We completed it by adding <code>role="listitem"</code> to the items. For the second, we added an <code>aria-label</code> that describes what the icon does:</p>
<pre><code class="language-html">&lt;a class="elementor-icon" href="#" aria-label="Open the contact popup"&gt;
  &lt;!-- icon --&gt;
&lt;/a&gt;
</code></pre>
<h2>What the four cases share</h2>
<p>None of these changed how the site looks. All of them were found by reading reports carefully rather than by browsing the site. A habit that helped: after each fix, re-run the same report and confirm the specific warning disappeared, instead of assuming it did.</p>
<h2>About us</h2>
<p>We're <a href="https://shahreweb.com">Shahre Web</a>, a digital marketing agency that treats branding, WordPress web design, SEO and social media as one growth path. Technical cleanups like these are part of how we build and maintain WordPress sites. If you'd like to talk about your own project, the initial consultation is free: <a href="https://shahreweb.com">shahreweb.com</a>.</p>
]]></content:encoded></item><item><title><![CDATA[What We Learned Tuning an Elementor Homepage for Core Web Vitals]]></title><description><![CDATA[Practical notes from optimizing a WordPress and Elementor homepage: LCP discovery, icon fonts, font-display and why lab results fluctuate.]]></description><link>https://shahreweb.hashnode.dev/what-we-learned-tuning-an-elementor-homepage-for-core-web-vitals</link><guid isPermaLink="true">https://shahreweb.hashnode.dev/what-we-learned-tuning-an-elementor-homepage-for-core-web-vitals</guid><category><![CDATA[Core Web Vitals]]></category><category><![CDATA[Elementor]]></category><category><![CDATA[SEO]]></category><category><![CDATA[web performance]]></category><category><![CDATA[WordPress]]></category><dc:creator><![CDATA[shahreweb]]></dc:creator><pubDate>Sun, 22 Nov 2026 10:53:10 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6b02c74ac8790508fabb6fa7/f9c0a0db-1260-4ec7-a914-19954d64b315.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>When we tuned the homepage of our own WordPress site, most of the lost time was not in the places we expected. It was in a few small decisions: how one image was loaded, how fonts were declared, and how CSS was delivered. Here are the notes, in the order we found things.</p>
<p>The site is built with WordPress and Elementor, with a lazy-loading plugin and page caching in front of it. We measured with PageSpeed Insights, mostly on mobile.</p>
<h2>1. The LCP image was not discoverable</h2>
<p>The largest element on mobile was the hero banner image. The LCP breakdown showed most of the time was <strong>resource load delay</strong>, not download time. The reason: the lazy-loading plugin had rewritten the image so its real URL lived in a <code>data-src</code> attribute and was set by JavaScript. The browser could not find the image in the initial HTML.</p>
<p>The fix has two parts:</p>
<ul>
<li>Exclude the above-the-fold image from lazy loading.</li>
<li>Mark it as high priority.</li>
</ul>
<pre><code class="language-html">&lt;img
  src="/path/to/hero-mobile.webp"
  width="705" height="1057"
  fetchpriority="high"
  decoding="async"
  alt="Hero banner"&gt;
</code></pre>
<p>In our case this cut the resource load delay from roughly 2.2 s to roughly 0.8 s. But total LCP barely moved at first, because the bottleneck had shifted from discovery to download. That led to the next step: compressing the image itself (we got the mobile hero down to around 80 KB).</p>
<p>One detail that cost us time: Elementor serves resized copies from a <code>thumbs</code> folder with hashed file names. If your plugin's exclusion list uses the original file name, it may not match. A partial name worked better than the full one.</p>
<h2>2. Fonts: format, preload and <code>font-display</code></h2>
<p>We were preloading the same font in two formats (<code>.woff</code> and <code>.woff2</code>), so two requests competed with the LCP image. Keeping only <code>.woff2</code> preloads helped. We also declared fonts explicitly with <code>font-display: swap</code>:</p>
<pre><code class="language-css">@font-face {
  font-family: "MyFont";
  src: url("/fonts/MyFont-Regular.woff2") format("woff2");
  font-weight: 400;
  font-style: normal;
  font-display: swap;
}
</code></pre>
<p>Be careful with <code>swap</code>: if a heavy font arrives late, the text reflows, which can create layout shift. Check the "Layout shift culprits" insight after changing it.</p>
<h2>3. Icon fonts can quietly cost more than text fonts</h2>
<p>Two icon fonts, one around 350 KB and one around 120 KB, were loading as <code>.ttf</code>, and they contained far more icons than the site used. The icon CSS even listed <code>ttf</code> before <code>woff</code>, so the browser picked the larger format. We converted them to <code>woff2</code> and overrode the <code>@font-face</code> order. A better long-term fix is subsetting to only the icons you use, or switching to inline SVG.</p>
<h2>4. CSS delivery in Elementor</h2>
<p>By default, Elementor outputs per-page CSS as external files. On our site that created a chain of render-blocking requests. Switching the CSS print method to internal embedding removed that chain, at the cost of a slightly larger HTML document. It is worth testing on your own pages, since the trade-off depends on how large the CSS is.</p>
<h2>5. Small checks that are easy to forget</h2>
<ul>
<li>Set explicit <code>width</code> and <code>height</code> on images to avoid layout shift.</li>
<li>Make sure unknown URLs return a real 404, not the homepage. A soft 404 can confuse audits and crawlers.</li>
<li>Check that <code>robots.txt</code> is valid and not blocking assets you need.</li>
</ul>
<h2>A word of caution about lab data</h2>
<p>Lab results on PageSpeed Insights swing a lot between runs. On the same page, within the same hour, we saw LCP values anywhere from about 2.5 s to nearly 8 s. Before you celebrate or panic, run several tests, compare the LCP breakdown rather than only the score, and wait for real-user (field) data when it becomes available.</p>
<h2>Checklist</h2>
<ol>
<li>Find your LCP element and confirm it is in the initial HTML.</li>
<li>Exclude it from lazy loading and set <code>fetchpriority="high"</code>.</li>
<li>Compress it and serve a size that matches the viewport.</li>
<li>Keep only the font formats and weights you actually need.</li>
<li>Convert or subset icon fonts.</li>
<li>Re-test several times and look at the breakdown.</li>
</ol>
<h2>About us</h2>
<p>We're <a href="https://shahreweb.com">Shahre Web</a>, a digital marketing agency that treats branding, WordPress web design, SEO and social media as one growth path. Performance work like this is part of how we build and support WordPress sites. If you'd like to talk about your own project, the initial consultation is free, and you can reach us through <a href="https://shahreweb.com">shahreweb.com</a>.</p>
]]></content:encoded></item></channel></rss>