Izaac Barratt shares practical Shopify performance advice, including ways to make online stores load faster by prioritising important page content and delaying less urgent scripts and apps.
Most useful for practical Shopify speed advice and technical guides for high-revenue stores.
Best for
A campaign selling Shopify performance work to high-revenue stores needing a technical guide.
Not for
Paid consumer brand partnerships, sponsored posts, product seeding, or reach and awareness campaigns.
Key takeaways
Place key product imagery ahead of popups and app scripts.
Load an app only on pages that need it.
Speed work pays only when demand and offer already work.
Check first: Ask for completed case study, audience data, and delivery terms before contacting.
Main ideas
Load order, not file count, decides how slow a store feels · What shoppers perceive matters more than what the file size says · Speed work only pays when demand and the offer already work
Izaac Barratt shares practical advice on improving Shopify store performance.
The five posts focus on when speed work is worthwhile, how to prioritize apps and page assets, and techniques such as lazy-loading video.
Their concrete explanations of how loading order affects the visitor experience, alongside examples of reported store results, make their work useful to follow.
Barratt explains performance as a question of what visitors see first, not simply how many files a store contains.
One post recommends placing key product imagery ahead of popups and app scripts, and loading an app only on pages that need it.
Another uses a cafe analogy to explain why speed may matter less than product appeal and demand until customers are already waiting.
These examples make technical choices and their limits easier to understand.
Barratt also reports results, including a product page changing from a nine-second load to about two seconds with a 15% conversion-rate increase.
The posts do not independently verify these results.
A short post about a nine-figure store is only a pre-launch announcement; its case study is pending, so ask for the completed case study before assessing results.
Izaac Barratt writes about speeding up Shopify stores.
Read more
Across the posts reviewed here, the argument is consistent: slowness is mostly about which assets load in the first seconds of a page, not how many files or apps a store has.
The standard fix is to reorder or defer work rather than delete it.
Barratt says this is the highest-return project only for brands with real demand, enough traffic and a settled offer.
Several posts report conversion gains for apparel stores after load-order changes.
The most recent technical item describes a platform-level change to video loading, while a large rebuild is announced with results still to come.
Load order, not file count, decides how slow a store feels
Barratt argues that pages feel slow because images, scripts and apps all download in the first couple of seconds and crowd each other out, while browsers cannot tell which videos or assets are off screen.
Read more
The remedy is to control load order: only what a shopper sees should download in that critical window; everything else can wait.
Since apps rarely expose a priority setting, they suggest asking the vendor for a manual code snippet and placing it lower on the page.
This also lets an app run only on the page types that need it.
In a pre-BFCM post, Barratt notes that a size-guide app is only needed on product pages, so moving its script prevents it from downloading elsewhere.
They compare the first seconds to rush-hour traffic versus 3am traffic: the road is the same width, but the congestion is not.
They report making pages two to three seconds faster in roughly ten hours of back-and-forth with app vendors, without deleting anything, and a 15% conversion-rate increase for an apparel brand.
What shoppers perceive matters more than what the file size says
Barratt distinguishes physical from perceived speed: total files and file size can stay exactly the same while the experience changes completely, if the main visuals arrive first and loyalty, tracking and feature scripts follow.
Read more
Shoppers need the product imagery, not pop-up or analytics scripts. The aim is to make waiting less painful, not rebuild the store.
A product page that took nine seconds to load was reorganised to load in about two seconds without removing anything.
Barratt reports conversion up 15% within a week, describing higher margins because the same ad spend now converts better.
They compare the experience to being served appetisers while waiting 46 minutes for a main course, versus waiting outside and then being seated with the order taken immediately: the wait is the same, but it feels different.
Speed work only pays when demand and the offer already work
Barratt cautions against treating site speed as an automatic win.
Read more
Before investing, a brand should have enough traffic, a product people return for, and pricing or messaging that is no longer being tested.
When those conditions hold and slow journeys are visibly costing visitors, speed can be the highest-leverage change: it affects every page and journey at once, with little risk because the store looks the same afterwards.
They also rate it above small conversion-rate tests, arguing that a speed change is a bigger test than a 1-2% tweak.
Barratt uses a cafe analogy: a new cafe should first ask whether enough people come in, whether they like the coffee and buy a second cup, and whether the price puts them off.
Only then is time-to-serve worth measuring.
Their practical checks are revenue above $5M a year, a site that is measurably slow, and no outstanding offer or messaging tests.
Conversion lifts of 10-20% appear mainly where real demand and heavy cold traffic, often from Meta ads, make visitors impatient.
Video should load on demand, through the native player
Barratt calls video the heaviest single drain on a store's loading budget: a video is effectively dozens of images every second, and browsers download it even when it's off screen, hogging bandwidth needed by visuals.
Read more
The first fix is lazy loading, so a video downloads only once it enters view.
A further step is video facades, which download nothing until a visitor presses play, since most videos are never watched.
They recommend keeping video on Shopify's native player rather than using third-party embeds.
For an apparel brand that ran a video campaign across its site, Barratt says they manually lazy loaded videos in January, before the feature existed, cutting page load by 76% and lifting conversion 26%.
The capability has since been built into modern browsers and added to Shopify.
They recommend rendering videos with video_tag in Liquid and avoiding Vimeo or YouTube.
Pages most affected include product pages with stacked user-generated video, collection grids with intermittent video, and homepages with large brand video.
Defer first — but the biggest rebuilds remove code as well
Across the posts, the recurring method is deferral: change the order in which things load, keep every app and file, and change nothing else.
Read more
One announcement describes a large project on a nine-figure store where more than 100 files were changed and roughly 4,000 lines of code removed, showing that reordering alone may not be enough at the largest scale.
Published the day before the work went live, this short pre-launch note expects key pages to be at least 45% faster.
It gives no method detail, and the case study is pending.
Ask for the case study and results before relying on the claim.
Most posts frame the work as making a store faster without deleting anything. One large-rebuild announcement instead describes removing code; its results are still outstanding.
Answers the first question a team should ask: is site speed worth addressing on this store?
Read more
Newcomers should start here; it sets the conditions the rest of Barratt's work assumes instead of jumping straight to a technique.
Izaac Barratt argues that speed work is not for every store, and offers three checks before investing: annual revenue above $5M, a site that is measurably slow (suggesting Fastersite), and no outstanding offer or messaging tests.
The cafe analogy runs through the post: a new cafe should first find out whether people like the coffee and come back before optimising serving time.
A 10-20% CVR lift is possible when demand is strong and queues form — meaning plenty of cold traffic, typically from Meta ads, and visitors becoming impatient.
Barratt sets speed work against CRO: speed affects every page and journey, making it a bigger test than a 1-2% conversion tweak, with little risk because the visuals do not change.
For brands planning a campaign
For a technical guide to high-revenue e-commerce performance, this offers a clear qualifier: who should act, what to measure first and how to avoid promising a lift to a store with a demand problem. It also makes the case that speed is the biggest single test to run before smaller CRO changes.
Explains how a heavily app-laden store can get faster without removing anything — the constraint most merchants raise first.
Read more
Start here for the method behind the speed gains in the other posts.
The problem is not the number of apps; it is that every app competes for the first seconds of page load.
Barratt compares it to rush-hour versus 3am traffic: the page feels slow at first because everything downloads at once, then speeds up as congestion clears.
The fix is to control app-script placement so only priority assets — the main product image, for example — load in the critical window, while popups, chatbots and loyalty scripts wait.
Most apps do not offer a priority setting, so Barratt suggests asking the vendor for a manual code snippet and placing it lower on the page.
Page-level control offers another benefit: a size-guide app can be limited to product pages so it never downloads elsewhere.
The claimed result is pages 2-3 seconds faster after about 10 hours of back-and-forth with vendors, and a 15% CVR increase for an apparel brand, with nothing deleted.
For brands planning a campaign
This is the set's most reusable operational procedure: step-by-step instructions for a guide (approach the vendor, obtain a snippet, place it manually, restrict it by page type) and a before-and-after metric a brand can replicate. Its page-level control also expands a performance brief from homepage speed to per-template optimisation.
Explains the commercial return and why the underlying idea is perception, not file size.
Read more
Start here for the number and conceptual frame in one place.
A product page that took 9 seconds to load was reorganised to load in about 2 seconds, with CVR up 15% in a week and results visible in about 1.5 weeks.
Barratt frames the gain as higher margins because ad spend is unchanged: the same traffic converts better.
Nothing was deleted, and total files and file size stayed the same; what changed was what arrived first.
Visuals take priority, while loyalty, tracking and feature scripts load in the background.
According to Barratt, users need the main visuals, not tracking scripts or popup apps.
The analogy contrasts being served appetisers while waiting 46 minutes for a main course with waiting outside, then being seated and having your order taken immediately.
The suggested technique is deferring scripts.
For brands planning a campaign
Gives a guide the ROI framing that matters to a brand owner — better returns on existing traffic, not new spend — plus a concrete before-and-after pair and a simple explanation of perceived versus physical speed to test on a merchant's own pages.
Explains what changed at platform level and what stores with heavy video should do now.
Read more
Start here for the most current technical item: it describes a feature that did not exist when the earlier work was done.
Videos are enormous files — Barratt notes they are effectively 30 images per second — and browsers cannot tell which videos are off-screen, so everything downloads immediately and consumes bandwidth.
Lazy loading means a video downloads only when it is on screen: pay-as-you-go network use instead of downloading everything up front.
Barratt says the technique was implemented manually for an apparel brand in January, before the feature existed; lazy loading videos cut page speed by 76% and raised CVR by 26%.
The feature is now built into modern browsers and added to Shopify.
Barratt advises using Shopify's native video player rather than Vimeo or YouTube, and rendering videos with video_tag in Liquid.
The post also covers a more advanced step, video facades, which load a video only when play is pressed, on the basis that most videos are never watched.
The approach is relevant to pages with heavy visuals, product pages with multiple UGC videos, collection grids with video and homepages with brand video.
For brands planning a campaign
Adds a dated, platform-native item to a technical guide and a clear rule for brands: use the native player and consider facades for decorative video. The 76% and 26% figures give video-heavy brands a reason to audit their PDP and collection templates.
Shows the scale of engagement Barratt takes on and what a large rebuild looks like.
Read more
Start here for context only: the post is a pre-launch note, not a lesson.
A short announcement says a rebuild goes live the next day, with more than 100 files changed and around 4,000 lines removed to speed up a nine-figure Shopify store.
Barratt expects key pages to be at least 45% faster and says the case study is pending.
The post gives no method details, before-and-after metrics or client outcome.
For brands planning a campaign
Shows that Barratt's work reaches large-volume stores and involves removing code, not just deferring it. The promised results and case study are not included, so ask for the completed case study before relying on the scale claim or citing a figure.
Barratt argues that page speed depends not just on how many files or apps a store has, but on which assets load first.
Read more
They recommend showing the main product image before pop-ups or chat tools, then loading less urgent scripts in the background. A restaurant-waiting analogy explains why the order of events can make the same wait feel shorter.
Explains technical sequencing with everyday comparisons and a concrete implementation step.
For brands planning a campaign
A technical guide could show high-revenue brands how to audit loading order and work with developers to defer nonessential scripts without removing useful store features.
Barratt describes videos as a source of network congestion, especially on product pages, collection grids and homepages.
Read more
They recommend native Shopify video with lazy loading, so videos load when they enter view, and describe video facades as a further option that waits for a visitor to press play.
Names the affected page types, explains the mechanism and gives developers a next step.
For brands planning a campaign
For visually rich brands, pair page-type examples with implementation options and explain that the right approach depends on how the store renders video.
Barratt cautions that site speed is not always the highest-return project.
Read more
They say brands should first consider whether they have enough traffic, a product people want, and an offer or message that is ready; speed becomes a stronger priority when slow journeys are causing visitors to leave. The cafe analogy distinguishes improving the experience from fixing the main business constraint.
Uses a qualification checklist and an analogy to connect technical work to business readiness.
For brands planning a campaign
A performance guide should help readers decide whether speed is their current bottleneck, rather than promise every store a conversion lift.
Barratt reports faster page loads and higher conversion in apparel-brand examples, including a post that says a project produced a 15% conversion-rate increase.
Read more
Another post describes a large Shopify project and says its case study is pending. Ask for the case study and supporting evidence before presenting these reported outcomes as verified results.
The post about the nine-figure Shopify project says a case study is pending and does not yet provide results.
For brands planning a campaign
Use the examples to make the advice concrete, distinguish reported outcomes from independently documented evidence, and avoid presenting them as guaranteed results.
Izaac Barratt's posts describe hands-on Shopify performance work for apparel and other direct-to-consumer stores.
Read more
They name Shopify and fastersite.ai, which Barratt recommends for checking whether a store is actually slow, but do not identify the clients or state whether any brand or tool has a paid or formal relationship with them. Ask for client names and details of any commercial ties.
Shopify
Mention
Barratt advises on performance for Shopify storefronts.
Read more
The posts reference Shopify's native video player and its lazy-loading feature, and explain how app scripts and images compete for load time.
A practical check for e-commerce managers weighing speed work: use the tool to establish whether the site is genuinely slow before spending on performance.
Izaac Barratt's posts explain why Shopify stores feel slow and what to change first.
Read more
Their central argument: the opening seconds of a page load are a competition for bandwidth, so the fix is to decide what loads first rather than delete apps or files.
Three useful entry points are the pre-BFCM post on holding app scripts back and asking vendors for a manual snippet; the post on video, which calls off-screen video the heaviest single drain and recommends native Shopify playback with lazy loading and play-triggered facades; and the post on when speed work is worth paying for: when a store has enough traffic, a product people return to and an offer that is no longer being tested.
A short pre-launch note about a nine-figure rebuild is an outlier: it describes code removed rather than reordered, with results still to come.
For Shopify conversion design, Md Moktadir Hossain writes about landing-page layout, value propositions and trust signals for store owners.
Najmah Salam teaches content marketing and positioning to indie game developers through talks and writing.
For AI-produced ad creative, Grace Eva explains how brands generate UGC-style video without a creator or camera.
Both work with Shopify stores that get traffic but do not convert.
Read more
They write short posts that challenge a common assumption about why a store underperforms, list specific problems and offer to review a reader's page or store. Both address store owners directly and judge the work by conversion, not design polish.
Hossain advises on page design and messaging: hero sections, headlines, reviews, a single call to action and mobile layout.
The examples are qualitative.
Barratt's technical posts explain load order, script position and which page types a script should run on.
They give developer-facing instructions, such as rendering video with video_tag, and report measured conversion changes after specific updates.
Both teach marketing to a defined audience through frameworks and analogies rather than generic tips.
Read more
Barratt uses rush-hour traffic and appetiser-versus-wait analogies; Salam frames the audience as the hero and content as a waterfall. Both give readers something portable: a step to pass to a developer or a talk to watch.
Salam focuses on content marketing, positioning and planning for indie game developers, through conference talks and slide decks about what to say and when.
Barratt focuses on ecommerce store performance, with technical changes tied to measurable speed outcomes.
Izaac Barratt’s LinkedIn posts cover Shopify performance, including prioritising page content and delaying scripts or videos, making them relevant to briefs for technical guidance aimed at Shopify teams.
Read more
To assess professional audience fit, ask for recent audience survey results or another documented source showing viewers’ roles, seniority and employer types; use platform audience data separately for age, gender or geography.
Izaac Barratt’s five posts offer performance consulting, not partnership packages.
Read more
Each explains a Shopify speed problem and its fix: deferring app and script loading, lazy-loading video, or prioritising visual assets.
Results are presented as client outcomes, including a 15% conversion lift for an apparel brand after page load times fell from about 9 seconds to about 2 seconds.
Two posts point readers to a separate guide or tutorial; another invites them to comment for a recommendation on whether to defer a given app.
The posts target store owners and e-commerce managers, using lead generation rather than a published sponsorship proposition.
A buyer interested in a sponsored placement, paid technical walkthrough, or branded collaboration should ask about terms directly; the posts provide no rate card, media kit, sponsorship policy, deliverable specifications, or paid-partnership contact route.
A campaign aimed at high-revenue Shopify stores, selling Shopify performance work and needing a technical guide — how to make a large Shopify store faster before peak trading — to publish under its own name or co-brand with a practitioner.
Read more
Izaac Barratt is a good fit because the posts cover the guide in pieces.
The five posts explain how to tell whether speed work is worth doing (annual revenue above $5M, a measurably slow site, and no offer or messaging tests still pending); how to defer app and script loading so main product imagery loads first; how to lazy-load video through the native Shopify player rather than Vimeo or YouTube; and why perceived speed matters more than total file size.
Each post tackles a narrow question with a comparison and an implementation step a developer can act on.
That combination suits a guide for e-commerce managers as well as developers.
Barratt ties technique to a business decision — is the store’s bottleneck speed or demand? — a step many agency guides skip, and one readers need before spending budget.
The posts also offer natural handoffs: two point readers to separate tutorials, and one invites them to comment for a recommendation on a specific app.
The conversion and speed figures (up to 26% CVR, 76% faster page load, 9 seconds down to about 2 seconds) are Barratt’s reported results, not independently documented.
The nine-figure rebuild post describes its case study as pending.
No client names, employer, agency or delivery terms appear in the posts; ask who would deliver the work and request the completed case study before co-publishing.
Present any expected lift as a reported outcome and a hypothesis to test on the reader’s store, not a guarantee.
When to choose a specialist
A paid creator partnership for a consumer brand or retailer — sponsored posts, product seeding or affiliate placements — to put a product in front of a broad shopping audience, measured on reach or awareness.
Read more
The posts don’t support that brief.
They offer technical advice to store operators and e-commerce managers on reorganising load order, deferring app scripts and lazy-loading video.
No sponsorship formats, rates, deliverables or partnership contact route appear; the only calls to action are a comment thread and tutorial links.
The audience section provides topic information but no published data on who reads or watches, including roles, seniority, employer size or geography, so a reach or awareness plan cannot be sized.
There is a sharper mismatch: Barratt says speed work pays off only for stores that already have demand and traffic, and advises readers not to expect a conversion lift unless they fit the criteria.
A consumer-facing seeding campaign targets people who are not store operators or deciding whether to optimise a storefront, so the expertise that makes Barratt useful for a technical guide does little for this brief.
LinkedIn is the only channel mentioned, with no information about video, newsletter, event or other formats for a consumer campaign, and no named clients or brand relationships.
If a consumer-facing partnership is still of interest, ask Barratt directly about formats, terms, reach and audience composition before planning it.
A worked campaign example
A worked angle: a “Fix the load order before peak” technical guide, co-published by the agency with Barratt.
Promise: make a high-revenue Shopify store measurably faster without deleting apps or redesigning the storefront, in the two to three weeks before peak trading.
Structure, with the reason each part exists: 1. Qualification checklist, based on Barratt’s “right time” post — revenue above $5M, a measurably slow site, and no outstanding offer or messaging tests. Purpose: filter readers before they invest, making the rest of the guide credible rather than salesy. 2. The load-order explanation — rush-hour versus 3am traffic, and appetisers while waiting for the main course — to show how the same files and wait can feel very different. Purpose: explain the concept to a non-technical buyer in one screen. 3. App deferral procedure: ask the vendor for a manual snippet, paste it lower on the page rather than using the theme app slot, and restrict apps by template so a size-guide app loads only on product pages. Reported before and after: about 9 seconds to about 2 seconds on a product page, and 2–3 seconds faster after roughly 10 hours of vendor round trip. 4. Video handling: use the native Shopify player rather than Vimeo or YouTube, lazy-load so video downloads only when on screen, and consider facades that wait for a play press. Name the affected page types — product pages with user video, collection grids, homepages with brand film. 5. Self-audit checklist and one handoff: a short series of yes/no checks a store team can run this week, ending in a booking link for the agency’s speed audit.
Copy rules: attribute every number to Barratt rather than stating it as fact; don’t turn their reported 15% conversion lift into a promise; and don’t cite the nine-figure rebuild beyond its scale, because its case study is not yet published. Ask Barratt for the completed case study and permission to describe the apparel example before publication.
Afterwards, readers should be able to run the checklist, decide whether speed is their bottleneck, and know what to ask their developer next. Hold the guide to that test.
Choose Md Moktadir Hossain when the agency's guide is about the landing page as a sales engine, not page-load time.
Read more
Both posts offer the same diagnosis a store team can run before spending anything: confusing layout, no clear value proposition, weak product presentation, too many distractions and no visible trust signals.
Hossain puts the test plainly: if a landing page cannot answer what you sell, why a buyer should trust you and why they should buy now within five seconds, traffic is being wasted.
The fixes are concrete and inexpensive: a focused hero, product storytelling, reviews as proof, one call to action instead of five, and a mobile-first layout.
For a guide aimed at high-revenue stores where the bottleneck is a muddled page rather than a slow one, this is the closer match.
The campaign decision remains the same — publish a practical storefront-improvement guide under the agency's name for e-commerce managers — but the focus shifts from script order to page structure.
The advice focuses on page design and content.
Izaac Barratt's posts offer no guidance on deferring app scripts, lazy-loading video or measuring whether speed work is worthwhile, so a store with genuine performance problems gets a checklist, not a fix.
They also give no qualification criteria or before-and-after numbers.
One says UI changes raised landing-page conversion without increasing traffic, but names no store, date or measurement.
Both posts end by inviting readers to comment for a page review, making the material a lead-in to Hossain's own service rather than a documented case.
A guide based on this material would need independent support for any performance claim; treat any expected conversion lift as a hypothesis for the reader's store.
Choose Najmah Salam when the campaign shifts from fixing a storefront to building an audience around a launch.
Read more
The posts cover marketing planning that a performance guide does not: creating one substantial piece of content and remixing it into GIFs, a written devlog and short videos for several weeks; making players the heroes of the story and the marketer their guide; and sharing work in progress — concept art, funny bugs and problem solving — to build trust before release.
Salam also has talks to point to: sessions on positioning a game and on twelve content marketing tips, delivered at named events, with slides available to download.
For an agency planning a speaker-led webinar or co-authored guide on content across a launch calendar, the working examples and demonstrated presentation skills give the guide something Barratt's performance posts do not.
The subject is indie game marketing, not e-commerce.
Izaac Barratt's posts do not address Shopify, page speed, conversion rate or store-side measurement, so store operators would have to translate the advice before acting.
The tactics target player outreach over a long development cycle, a different budget and timeline from a peak-trading speed project.
A guide built around Salam would need its store context written from scratch, and the agency would be choosing a launch-planning angle instead of the speed-and-conversion angle Barratt's work supports directly.
Choose Grace Eva when the client's problem is producing more paid-social creative faster, not speeding up the store.
Read more
The posts describe an AI-assisted production process with no creator or camera: AI avatars that resemble creators, script and voiceover generation, product demos and B-roll, captions, and multiple ad variations for testing.
Eva presents the value as faster creative testing — testing more hooks, product angles and concepts instead of waiting days or weeks for new creator footage.
They also outline a workflow from idea through script, video, testing and optimisation, plus guidance on choosing an AI tool.
For a guide aimed at agency clients investing in paid social who want more variations to test, this directly addresses the creative half of their growth problem.
The campaign decision remains the same: publish a practical guide under the agency's name for e-commerce brands.
This material does not address storefront performance.
Izaac Barratt's posts do not mention page speed, script order or store conversion, so the guide would not help readers wondering why a product page takes nine seconds to load.
One post names Tagshop AI as a tool for turning product ideas into UGC-style ads, making the material tool-led; take care before presenting it as neutral advice.
Neither post reports a measured campaign result, so any claim that faster testing improves performance would need to be framed as a testing approach, not a proven outcome.
This page draws on the full text of five LinkedIn posts by Izaac Barratt about Shopify store performance, together with the public LinkedIn profile linked from the page.
The posts cover when speed work is worth doing, deferring app and script loading, a product page rebuild reported at nine seconds down to about two, lazy-loading video through Shopify's native player, and a short pre-launch note about a large rebuild.
The posts do not give publication dates; the profile was viewed on 8 October 2026.
The conversion and speed figures in the posts are Barratt's own reports, not independently verified, and the large-rebuild post describes its case study as pending.
The posts do not mention video, screenshots, transcripts, client names, employer, agency or commercial terms, and nothing in them establishes other signature work such as a book, show or business.
Where the page compares Barratt with other creators, those judgments rest on the posts considered for each of them.
