E2 Lighting Review

A read-only check of 18 category pages found 106 blank product-image card occurrences across 67 products. In 94 of those occurrences, WooCommerce already returned a valid product image; the rendered category HTML still emitted an empty img src. On the Smart BLE category, the 12V PIR product has a valid WooCommerce image but renders blank.

Update the category card to use the WooCommerce featured image when the custom image field is empty. Test the Smart BLE category and representative categories before changing cache settings.

The WooCommerce Store API reports no images or featured media for these two products, and their product pages show the WooCommerce placeholder. The 12V PIR record is different: it has a valid image and is primarily a category-template problem.

Assign and verify the correct product images for these two products. Do not substitute visually similar media without confirming the product match.

Five product records reference four old PDF URL families that return 404. Each family has a confirmed replacement returning 200: the WP28 spec sheet, PCOM commercial downlight sheet, tunable flood-light sheet, and DL-SLIM V2 sheet.

Replace the four stale PDF references in the affected product content, then verify every new URL and its product context.

The product short description contains an http://localhost/e2lighting/... PDF URL alongside a relative data-sheet link. The localhost URL does not resolve for production visitors.

Replace the localhost reference with the correct production PDF after confirming which data sheet belongs to this product.

Additional legacy upload paths return 404 in current page content. Two exact media matches were identified in the Media Library; the remaining old references need product-level confirmation before replacement.

Replace only exact, verified media matches. Review ambiguous references with E2 before changing them or removing the content.

Full WordPress/WooCommerce admin access is enough to assign the two missing product images, replace the verified stale PDFs and image URLs, purge the cache, and verify the affected pages.

These content fixes are available now. We should take a backup and get approval before editing production.

With the current WordPress admin access, we can reproduce the blank cards, inspect the active theme/plugin configuration, and compare each WooCommerce record with the rendered HTML. The 12V PIR record has a valid image, but the category card emits an empty image source.

If the card logic is not exposed through the dashboard, staging plus SFTP/SSH or the theme repository would let us patch the template safely.

Full WordPress admin access lets us open NitroPack, purge and rebuild caches, test the available cache and lazy-loading settings, and run before-and-after checks. The category page is cached, but the homepage is explicitly excluded and the lazy-loading layer is involved in image rendering.

We can exhaust the NitroPack controls available in WordPress first. If the remaining work requires account-level rules, theme code, or frontend changes, NitroPack account access plus staging/code access would let us reduce duplicate reCAPTCHA loads and the script payload safely.

We can measure public TTFB and API timing. The origin identifies as Apache; the homepage takes roughly 1.3–1.5 seconds to first byte and the Store API takes roughly 1.5–1.7 seconds.

We can continue measuring the public site while we work through WordPress and NitroPack. Ionblade control-panel access or host support would be needed to inspect the plan, resource graphs, PHP workers, MySQL, OPcache, CPU/RAM/swap, and server logs; we should not recommend a larger plan until those metrics show a constraint.

A read-only WooCommerce capture returned 211 of 211 products, 89 supporting pages, and 148 assets. All 211 product pages returned HTTP 200. The isolated Felix preview is bound to that captured catalogue; E2's WordPress site and existing sample deployment remain unchanged.

Review the real preview, complete final question-answering and source-link QA, then add Felix to E2's website. The preview already uses E2's WooCommerce catalogue capture; this step is the website iframe deployment, not another catalogue connection.

Felix can answer from structured catalogue data while the category renderer, missing media, and stale document links remain separate website issues. Deploying Felix will not itself repair those templates or files.

Review the findings and Felix preview together, then decide which website repairs E2 wants implemented alongside the Felix website deployment. The catalogue binding and website repairs remain separate work.