Salla store design that sells: eight checks before you pay a designer, buy a theme or add code

A Salla store design sells when a phone visitor sees the product photo, the price, the buy button and one reason to trust you without hunting, and the page does not make them wait for megabytes of images and scripts first. Check those two things before you pay a designer, buy a theme or add code.

This guide is for owners of Salla stores in Saudi Arabia and the Gulf who are about to spend on design. On 1 November 2026 we loaded 22 live Salla stores on a phone-size screen, ran 54 autocomplete searches and four Google searches from a Riyadh location, and read ten of Salla’s own design pages. We sell SEO, not store design, so we say where that interest sits. The limits are at the end.

Free 5-point SEO audit before you redesign. Send us your store’s address. Within 48 hours a senior specialist sends you 5 prioritized fixes with the evidence, including what Google sees on your product pages and what loads before the buyer can act. Get your free SEO audit.

The short answer: five findings and what to do

What we found	What to do
Salla gives you themes, a wizard, an editor and an AI assistant. Of its ten design pages we read, 0 mention Core Web Vitals or structured data and 3 mention page speed.	Treat speed and markup as your job, not the theme’s.
On a 412 pixel phone screen, 19 of 21 product pages show a buy button in the first screen, 18 of them as a fixed bar, but only 4 show the price.	Ask for the price on the first phone screen, not only a buy bar.
Home pages weigh a median of 3.4 MB and product pages 2.4 MB on a phone-size load.	Ask for a before and after weight with every new section, app or pixel.
All 21 product pages print Product markup with price and availability, and each has a heading one.	Do not pay for what is already there. Make sure custom code keeps it.
Salla’s own AI assistant does not build the product page, cart or checkout.	Plan those pages yourself, and test the result on a phone.

What owners search, and what they find

The Arabic search «تصميم متجر سلة» returns ten suggestions, and most are about buying design: with CSS, professional, free, from a freelance marketplace, from a classifieds site, with AI, and storefront. In English, “salla theme” returns ten suggestions about themes, the theme store, a theme developer and a theme detector, while “salla store design” returns only itself. Nothing returned for the phrasings an owner with a problem would type, such as “salla store not selling” or «ضعف المبيعات في سلة». Of the 24 English and 30 Arabic phrasings, 6 and 9 returned anything. Demand for the owner’s real question is not visible in autocomplete, so we wrote this for the person who is about to decide.

On page 1 from Riyadh, the English searches show Salla’s own pages almost alone: the store design wizard, the interactive editor, a design guide and the theme store. The Arabic searches mix Salla’s pages and videos with agency, freelancer and marketplace pages that sell design. We found no neutral guide that says what to check before buying.

What Salla already gives you

Salla’s help pages, opened on 1 November 2026, describe five design tools:

• Themes. You pay once for a theme, with no monthly theme fee. You can try up to five themes at once on any paid plan, and some are made by Salla and others by outside designers.
• Store design wizard. A simple mode builds a full storefront for you and an advanced mode gives control of colours, fonts and layout. Its trust step asks for your return and exchange period, your social links and, for Saudi stores, your Business Platform number.
• Interactive editor. You edit sections on the live page, hide them without deleting them, and it works from a phone.
• Code. CSS and JavaScript customisation needs the Pro or Special plan and a custom domain.
• Mushammir, the AI assistant. It builds design components from a text description.

Salla also says that the verification number of a verified store shows in the footer automatically. For the owner this means the base is solid. The decisions left to you are which theme, what you add, and what it costs the page in weight.

What Salla’s ten design pages cover, and what they leave out

We read the body of ten pages: Salla’s design guide, the wizard, store identity, the editor, the theme store, the theme FAQ, code customisation, one theme page, the AI assistant page and the store performance page. Our counts, coded by hand and re-checked by script:

Topic	Pages that cover it, of 10
Trust information: returns, buyer protection, verification, badges	6
Page speed or load named as a design concern	3
What a product page should contain	2
Conversion measured with a report	1
Search engines or SEO named	2
Core Web Vitals, LCP or structured data	0

The design guide is about the eye: logo, colours, type, grid and photos. Its advice is clear and useful: one or two hero banners, one colour for every add to cart button, compress images before upload, and no text under 14 or 16 pixels on mobile. It says nothing about the structure of a product page or what loads first. The one page that measures results is the store performance page, with conversion rate, abandoned carts and landing page analysis.

The AI assistant page is the most direct. Salla says the assistant does not yet build a complete theme, the header and footer, or the product page, cart and checkout. It also says you are responsible for checking each component on mobile and desktop and for how it affects performance and load speed.

What 21 live product pages show

We loaded the home page and the first product page of 22 Salla stores that ranked on page 1 in our October searches from Riyadh for products such as abayas, watches, coffee equipment and handbags. One store showed no product link on its home page or category pages, so we measured 21 product pages. The browser was set to a 412 by 915 phone screen. We report sizes, counts and what is on the page, never loading times, because our machine is in Egypt.

Measure	Result
Home page transferred	median 3.4 MB, from 2.1 to 9.6 MB; 18 of 22 over 3 MB, 6 over 5 MB
Product page transferred	median 2.4 MB, from 0.5 to 7.1 MB; 13 of 21 over 2 MB
Requests on a product page	median 252
Share of bytes that are images and scripts	median 45% images and 33% scripts
Third-party hosts on a product page	median 24, from 9 to 32; 20 of 21 load three or more of the eight analytics and advertising tool families we looked for, among them Google, Meta, Snap and TikTok

These stores rank, so they are likely better than average. Their weight comes mostly from photos and from the tools their owners added, not from the platform alone, and that is where design choices show.

On the first phone screen of a product page, 19 of 21 pages show a buy button, and 18 of those keep it in a bar fixed to the bottom of the screen. Only 4 pages show the price, and 3 show price and button together. On the other 17 the photo gallery fills the screen and the price sits below it. We coded this by eye from screenshots, because our first automatic price test found prices that were not there. On 3 pages a banner promoting the store’s app sits on top of the buy bar when the page first loads.

Three details are good news. The main product photo is the largest element on all 21 pages, it loads eagerly on 20 and carries a high fetch priority on 17, which is what web.dev advises for the image that appears first. Every product page prints Product markup with price and availability, and 21 of 21 also print return policy and shipping details markup; 11 add ratings and reviews. Each has a heading one in the HTML that arrives from the server. Two details need attention: 125 of the 1,219 images on these pages have no alt text, on 12 of the 21 pages, and 3 of the 21 pages moved more than Google’s 0.1 layout shift target in both of our two lab loads, and 7 of 21 in at least one.

Eight checks before you pay for design

1. Start from your own numbers

Open the store performance page and write down the conversion rate, the abandoned carts and the landing page report for the pages you want to change. Good answer: a before number for each page and a date to compare. Warning sign: “a fresh look” with no baseline.

2. Try the theme before you buy it

Use the trial of up to five themes on a paid plan. Salla can preview a theme on a demo store or on your own store, so choose your own, load your real products and look at each on a phone. Good answer: two or three themes tried on your products. Warning sign: a purchase decided from screenshots.

3. Look at the first phone screen of a product page

Google indexes the mobile version of your pages, so the phone version counts for search as well as for shoppers. In our test, 19 of 21 product pages show a buy button in the first screen and 4 show the price. Ask the designer for a screenshot of the first screen of a product page at 412 pixels before you approve it. Good answer: photo, title, price, buy button and one trust line fit on a 412 pixel screen. Warning sign: a gallery that fills the screen and pushes the price below it.

4. Set a weight budget

Ask for the transferred size and request count of the home page and a product page before the work, and again after each slider, app or tracking pixel. Salla’s own AI page puts the check of load speed on the merchant. Google’s targets are an LCP within 2.5 seconds, an INP under 200 milliseconds and a CLS under 0.1, measured in Search Console’s Core Web Vitals report. Good answer: a written before and after for each change. Warning sign: a new homepage with no measurement.

5. Keep what Salla already prints

Google’s product markup lets results show price, availability, ratings and shipping information. All 21 pages we read already print it, and a heading one. Do not pay to add them, and ask that custom code does not remove them. Test one product page after every change. Our Salla SEO guide covers the settings, and Salla SEO apps or an expert covers what apps add. Good answer: a before and after check of the markup. Warning sign: a quote for schema as an extra.

6. Fix images properly

Salla’s guide asks for compressed photos of one shape and meaningful file names. Add alt text that describes the product, and never lazy load the main photo. Google’s guidance on lazy loading says content should load whenever it is visible in the viewport, and web.dev lists lazy loading of above the fold images as a pattern to avoid. Good answer: alt text on every product photo and the main photo loading first. Warning sign: a slider that loads every slide at once.

7. Put trust before checkout

Salla’s wizard asks for your return period, social links and Business Platform number, and its theme FAQ lists shipping, clear sales and return policies, support, secure payment, chat and a buyer protection policy as essentials. Check that the product page says what a buyer needs, not only a footer link. Good answer: return period, delivery time and payment options on the product page. Warning sign: policies that exist only in the footer.

8. Control code and AI

Code needs a plan and a custom domain, so ask who writes it, who maintains it when the theme updates, and who holds a copy. Our guide to hiring someone for Salla CSS or JavaScript lists seven things to settle before anyone gets access. AI components must be tested on mobile and for speed. Make one change at a time and note the date so the conversion report can be read. Good answer: a change log with dates. Warning sign: ten changes launched together.

When design is not the problem

If few people reach the store, a new design will not fix it. Look at traffic first with our guide to traffic without sales and the e-commerce SEO audit checklist. If you are choosing between platforms or builders, read Salla or Zid for SEO and how to choose an e-commerce development company. Our Salla SEO service works on what Google reads and how fast the page appears; it does not replace a designer.

How we checked, and the limits

On 1 November 2026 we ran 54 Google autocomplete searches with the Saudi setting (24 English, 30 Arabic; the suggestions come from a machine in Egypt, capped at ten). Four searches ran from a Riyadh location with personalisation off; we noted titles and addresses and report no positions. We read ten Salla pages and opened ten Google and web.dev pages, six of which are cited. We loaded 22 stores in Chrome set to a 412 by 915 phone screen, with a Pixel agent and Arabic as the language, and counted bytes with the browser’s own network log until four seconds after the page loaded. The stores are Salla stores that ranked in our October searches, so they are not a random sample and probably load better than average. We measured one product page per store, the first one linked from the home page; two of those addresses answered with a 301 redirect, so the raw HTML of those two was read at the address they point to. The first phone screen was coded by eye from screenshots. Salla was recognised from its asset address in saved pages. Layout shift is a lab number from one load and varies by run. We did not measure loading times, real users, sales or conversion for any store, and we name no store. A store changes: these are readings of one day. We cannot say that a given design raises sales.

Sources

Salla pages opened on 1 November 2026: E-commerce store design guide, Use the Salla store design wizard (3 September 2026), Customize your Salla store identity (11 October 2026), Design your store in real time with Salla’s interactive editor (29 August 2026), How the Salla Theme Store works (31 August 2026), Theme Store questions merchants ask most (27 October 2026), Customize your Salla theme with CSS and JS, Raed Theme (31 August 2026), Mushammir from Salla: AI store design (13 September 2026) and Track sales and visits on the store performance page (31 August 2026). Google Search Central, opened on 1 November 2026: Understanding Core Web Vitals and Google search results (10 December 2025), Fix lazy-loaded website content (10 December 2025), Intro to product structured data (10 December 2025) and Mobile-first indexing best practices (10 December 2025). web.dev: Optimize Largest Contentful Paint (31 March 2025) and The performance effects of too much lazy loading (31 March 2022). The 22 stores and the autocomplete and search readings are our own, and no store is listed by name.

Is your store’s design costing you sales on a phone? Our free 5-point audit shows what Google reads on your product pages, what loads before the buyer can act, and which fixes to make before you pay a designer. It is the first step of our Salla SEO service for stores in Saudi Arabia and the Gulf. No obligation, delivered within 48 hours. Request your free audit.