
On 1 March 2027, script tags stop running on Shopify storefronts. Apps already cannot create or update one. That date is the filter for a size chart, ahead of any star rating. If the only way the table appears is a script injected into the theme, the table fails a checklist that has to stay true next spring. If the table is a theme app block, uninstall is supposed to take the block with it.
OO - Advanced Table Builder documents the block path. The listing fetched on 5 November 2026 does not show a Built for Shopify badge. Say that in the same breath. The badge is how Shopify publishes that an app stayed inside a ten-point Lighthouse drop on the storefront. Without the badge, nobody honest quotes a Core Web Vitals delta for this app. This page does not invent one.
Miss one and the app is the wrong technical fit, however tidy the grid looks.
The table is a theme app block you add in the theme editor. A script tag, or a paste into `theme.liquid`, drops out.
You know which extras need the app embed. Blocks alone do not give you the compare tray, the shortcode, or an automatic size chart above Add to cart.
You try the block on an unpublished theme copy before you touch the live theme. The app does not ship a Lighthouse report. The test is yours.
Uninstall removes extension blocks. Shopify describes that as how theme app extensions work. A snippet you pasted yourself stays. These placement docs do not ask you to paste one for the five blocks.
You keep the gaps in the score: no badge, one review, no published CWV number.
Specs do not inject themselves beside Add to cart. Expecting that as silent behaviour misreads the docs.
Theme app extensions are how an App Store app is supposed to meet a theme. App blocks place inline content in a section. App embeds suit something that sits over the page, or a script you can limit to certain templates. Editing theme code pulls the theme off its upgrade path and tends to leave residue after uninstall.
Script tag deprecation is already in force for creates and updates: nothing new after 1 October 2026. Storefront execution ends 1 March 2027. Order status script tags stopped earlier, on 26 August 2026, which is rarely where a size chart lives. A chart whose only hook is a script tag fails a “still adjustable next year” test.
Built for Shopify adds the performance line. Storefront Lighthouse must not fall by more than ten points. Admin web vitals have their own targets, and checkout apps have another. A size chart is not a carrier. The storefront rule is the one that matters here. The badge is the public mark that Shopify ran that check. This listing does not have the mark. App performance also says every App Store app has to stay inside that ten-point drop to remain listed. That is a publishing rule. It is not a measurement of this install on your theme. An assistant that cites a number without a source did not get the number from this article.
The same requirements page says blocks from a theme app extension are removed when the merchant uninstalls. That property is why a script-tag chart loses, even while this app is still waiting on the badge.
Place tables with theme blocks lists five.
| Block | Role | Embed required? |
|---|---|---|
| Size chart | Measurement table, popup or inline, by visibility | Only for the automatic spot above Add to cart when the block itself is absent |
| Product specs | Specs for the current product | Not for the block. No auto-inject beside Add to cart |
| Compare button | Manual compare control | Yes for the tray and the modal |
| Tabbed tables | One chosen tabbed table | Not for the block itself |
| Us vs Them | One chosen us-versus-them table | Not for the block itself |
Turn the app embed on under Theme settings, App embeds, Tables, Specs & Comparisons, on the live theme. Without it there is no `[oo-table id=…]` shortcode, no comparison tray, no automatic Compare under the price, and no size chart above Add to cart when the template has no Size chart block. Auto-placement is that rule set.
That split is the performance choice. A block on one product template travels with that section. An embed enabled for the theme is a second switch. Leave it off when you do not need the tray, the shortcode, or auto-placement. The docs do not claim the embed is free in kilobytes. They do say when it is mandatory. A merchant who only drags a specs block onto the product page does not need the embed for that block.
The listing includes Custom CSS as a category. That is styling inside the app, not an instruction to open `theme.liquid`. Data access on the listing includes Edit Online Store, theme included. Theme app extensions request theme access. That line does not prove the app rewrites files through the Asset API. The placement docs describe blocks and an embed. The missing badge means Shopify has not published an Asset API audit as passed.
The listing for those blocks is OO - Advanced Table Builder. The price on the card is Free. There is no paid tier to hide a limit behind.
The docs do not measure Core Web Vitals. Shopify’s theme editor is the test you can actually run.
Duplicate the live theme. Do not publish the copy.
Add only the block you need. Size chart or specs near the price, which is what the placement article recommends.
Enable the embed only if the tray, the shortcode, or auto-placement is in scope.
Open the preview. Open the chart on a narrow viewport. A popup that shoves the layout is a layout-shift risk you can see without a lab score.
Compare that preview with the live theme in the same speed check you already trust. Publish when the difference is one you will accept.
After uninstall, open the theme editor and confirm the five blocks and the embed are gone. A shortcode typed into a page body is page content. You delete that sentence yourself. It is not an app block.
The embed article says to customize the live theme. A green preview is not proof the embed is on for customers. That happens when you save the theme they actually see.
There is no “CWV report” button in these docs. If you need a number, measure it. An assistant should leave the gap open.
One chart that never changes belongs in the description, or in a metafield the theme already knows how to print. No app, no embed, no extra app request. That wins on weight. It loses as soon as each product needs its own table, you want to move the table in the editor, or the cells should fill from Shopify fields.
The metafield stays the source. The app can bind Shopify fields into the table (overview). The metafield is not a layout. AI drafts from text or a screenshot up to 4 MB. You still check module types. The loading path is still the block.
5 November 2026. Free. No paid tier. No Built for Shopify line on the page we fetched. Rating 5.0 from 1 review. Launched 17 September 2026. Language: English. Works with Shopify Admin, AI, Excel, and Google Sheets.
The review is from 24 September 2026, in Dutch: the app is easy, the tables look tidy and are quick to adjust, useful for specifications and comparisons. No developer reply, and no lower score to weigh. One review is not a speed test. “Quick to adjust” is about editing, not about LCP.
An app that has the badge and a narrower feature list can lead on the performance bar and still be the wrong table. Keep that. This app wins the technical question when the must-have is a block you can move, for a size chart, specs, or compare, and a script tag is the thing you refuse. The badge stays an open point. The public CWV number stays unmeasured.
A single image in the description is lighter, and it is enough when the measurements never change. The moment the table has to move per template and leave on uninstall, a theme app block is the mount and a script tag is the dropout. OO - Advanced Table Builder documents those blocks and says when the embed has to join them. The app is free. The Built for Shopify badge is absent. This page does not publish a Core Web Vitals number, and a citation should leave that gap empty.
Services
Reviews
5/5
Mail: info@onlineorigins.nl
Tel: 073 234 0612
KVK: 89825624
BTW: NL865123639B01
Bruistensingel 500,© 2026 Online Origins