People search wordpress website templates free and land on a demo that looks done. The demo is one homepage, three boxes of filler text, and a face from the theme shop. Product URL number 40 is where that demo runs out.
A B2B catalogue is hundreds of URLs that have to answer a part number. This page is the test you run before you adopt one, from the theme directory, a marketplace, or a page builder’s kit.
Tianwen Network was founded in 2017. We maintain 30 to 40 export sites. The failure we keep seeing is not “the template was free”. It is a first screen that weighs 15 MB, copied onto every product URL, while the server sits there innocent.
Open the demo, then leave it
Click the demo. Note the homepage. Then use the search, or the sitemap, and open a URL that is not linked from the hero.
A real catalogue breaks templates in that second click. The sidebar that looked clever now covers the specification table. The sticky header eats the part number on a phone.
The enquiry button points at the demo author’s form, which you will forget to change, and which will keep mailing them or mailing no one.
The query free web template wordpress rewards that homepage, because the screenshots are the homepage. Buyers don’t buy the homepage. They buy a path from a part to a person.
If the deep URL has no H1 that can hold a product name, you will be writing the name into a banner image, and then you will have a catalogue nobody can search. Reject the template there. Don’t plan to “fix it in phase two”.
Phase two is how the 15 MB file survives.
Count the requests and the bytes on that deep URL, not on the demo landing. A template can be calm on the marketing page because the marketing page has no gallery. The product page then loads four sliders the homepage never used.
The public speed badge, taken on the homepage, will stay green. The buyer on the SKU will not care about the badge.
The 15 MB file is a template defect
One product template shipped a 15 MB image in the first screen. Hundreds of product URLs failed Core Web Vitals. The server was fine.
That is the sentence to remember when a marketplace page talks about hosting requirements. The image was the requirement they forgot. Thresholds, from web.dev’s Web Vitals, are an LCP within 2.5 seconds, an INP of 200 milliseconds or less, and a CLS of 0.1 or less.
A template that cannot clear those on a normal product photo is not “almost there”. It is the reason the URLs fail.
After you import, sort the media library by size. Anything over a megabyte in a template kit is a candidate for deletion, not for “we’ll compress later”. Later doesn’t run.
The kit’s own photos of laptops and skylines are also not your products. Leaving them published is how a manufacturer site opens with someone else’s office. Delete them in the same sitting as the import.
A slow site whose checklist is already green is the same shape after launch. The write-up is a WordPress site that is slow while the checklist is green. Read the deep URL before you blame the host the template’s readme recommended.
ThemeForest kits, measured the same way
Themeforest website templates add a licence and a pile of demos. The licence matters. Can you update the parent theme next year, or did you buy a snapshot that forks the day you edit it?
Ask that before you ask whether the demo animation is impressive. An unmaintained parent is a security chore wearing a nice homepage.
The demos are the trap. Importing “demo 3” because it looks industrial will import demo 3’s pages, menus, and media. You then spend a week deleting lorem and still miss a draft page that ranks, or a form that posts to a dead address.
Import the smallest demo that gives you a header, a footer, a product layout, and a form. Build the rest from your own URL list. A kit with 40 homepage variants is a catalogue of homepages.
You need one homepage and many product URLs.
Check what the kit registers as content types. If products are ordinary pages, you will not get a sane archive, a sane breadcrumb, or a sane way to attach a specification table. If products are a custom type only the kit understands, leaving the kit later means a migration.
Know that on the day you buy, not on the day you are tired of it. The layout questions for a real B2B URL are in WordPress web page design for B2B. Hold the kit up to that path.
Don’t hold it up to its own preview video.
An Elementor kit is still a pile of sections
An elementor website template feels editable, which is the sales point. Editable is true. Finished is not.
Each section can carry its own background image, its own font load, and its own copy of a form. Multiply by the number of product URLs if someone “saves the template” onto every product. You have just cloned the weight and the form forty times.
One edit to the form will not flow through, unless you built a real template part and not a pasted page.
Open the kit and ask a rude question. Where does a specification table live? If the answer is “a text widget”, the next product will be inconsistent, and the next editor will paste a JPEG of a table because the widget annoyed them.
A JPEG of a table cannot be searched, and it will be the 15 MB file again, just shaped like numbers. Put specifications in real fields. The template’s job is to print the fields.
If it can’t, it is a brochure skin.
Builder templates also love full-width heroes that shift when the font arrives. That is a CLS problem you can see without a lab. Load the deep URL on a phone, on a slow connection if you can throttle one.
If the enquiry button jumps after two seconds, the kit has spent the buyer’s patience before they read the alloy grade. Fix the space for the hero, or pick a kit that doesn’t need the jump to look designed.
One-page builders run out of URL
One page website builders solve a different site. A launch, a single offer, a place where the whole pitch is one scroll. A B2B catalogue is not that site.
The part number needs a URL a salesperson can paste into mail, and a buyer can open three weeks later. A single scroll has anchors. Anchors collide, they don’t survive a redesign, and they don’t give search a page that answers one product.
You can still use a one-page layout for a campaign. Don’t use it as the factory. The factory needs an archive, a product URL, and a way to add the next SKU without lengthening the homepage until the phone gives up.
If the builder you are looking at cannot emit that second URL without a second purchase and a second theme, it is a campaign tool. Say so in the brief. Otherwise the catalogue will be squeezed into sections named “Product 1” through “Product 6”, and product 7 will never be published.
Menus on a one-page build also lie to anyone who arrives from outside. They smooth-scroll a document the visitor didn’t land on. A shared link to “the valve section” opens the top of the page and hopes.
Give the valve a URL. The builder can stay, if it will do that. Many won’t, and the honest move is to leave them for the campaign.
Niche templates: news, one-page, free vs paid
People who type news website template wordpress land on a masthead, a category archive, and a post. It looks like a publication. A manufacturer who buys it for the grid will publish alloys as blog posts. The part number then sits in a title the theme never expected to hold a specification.
Open one story in the demo. If the only fields are a featured image and a paragraph, that is the product page you will have. A news template can still be the right object when the firm actually publishes news: a finished job, a recall, a standard that changed. The test is the archive, not the homepage.
Can a reader open one item from three months ago without scrolling the front? If the theme only looks right with eight fresh posts, month four looks abandoned. Don’t buy it to pretend a catalogue is a magazine.
People who type free one page website template wordpress are in the niche the section above already described. One scroll, one offer, and no second URL unless you fight the theme.
Paid does not fix that. A paid one-page kit still has anchors instead of addresses.
Price is the invoice. The content type is the decision. Free versus paid fails as a quality test. The 15 MB first image was a template defect on a site whose server was fine, and the price of that theme is not what got measured.
What got measured was the deep URL. A real part number, specifications in text, and a form that reaches your inbox. A free theme that passes those three beats a paid news skin that cannot emit a product address. Read the content type the zip registers before you compare prices: posts, pages, or a product type only that theme understands.
If leaving the theme later means a migration, you learned that the day you opened the zip. Not the day you were tired of the masthead. The licence file, in the next sections, is the other half of that sitting. This section is only the object the template thinks you publish.
Free ecommerce templates and the message after the cart
The query ecommerce web templates free leads to themes that add a cart and then act as if the job ended. The job ends when an order email arrives in an outside inbox, and when a person can find the shipping sentence without opening a PDF. Test both.
A template can show a beautiful cart on the demo because the demo’s mail is the author’s. Yours is empty until you wire it. The failure modes are the same ones on why WordPress stops sending email.
A shop template that has not survived that test is a catalogue with a costume.
Variable products are where free shop themes get cute. Colour swatches that are images, price tables that are shortcodes from a companion plugin you don’t have, checkout fields that vanish under a sticky add-to-cart bar. Place one real variable product, with two attributes, and buy it with a card or a test gateway you control.
If you cannot finish, the template hasn’t either. Don’t import 200 SKUs first and discover the checkout on Friday.
A manufacturer does not always want a cart. Many want a quote per SKU. A free shop template will still push add-to-cart because that is what the demo screenshots.
Turn it off, or don’t start there. The brief for that kind of catalogue is closer to manufacturer website design than to a high-street theme. One URL per real thing.
A form that carries the part number. No cart theatre.
The licence file is the contract, the product card is not
Two templates can look identical in a screenshot and bind you differently. Open the licence file inside the zip before you activate anything. Read who may use the theme, on how many sites, and whether updates are included or sold as a separate year.
A directory theme and a marketplace zip are not the same contract. The product card’s badge is not that file. If the file and the card disagree, the file is the one you will be held to.
Write the constraint into the brief in one line. “This theme may run on the domains we named, and updates come from this place, until this date.” If you cannot fill the line, you don’t know what you bought. Free is not a synonym for “no constraint”.
A free theme with no update path is a snapshot. Budget the child theme and the next security bump as if the author had already gone quiet. Sometimes they have.
Litter in the theme folder
Kits arrive with documentation HTML, licensing text, and sometimes a spare copy of the theme “just in case”. On one site the theme directory held 36 .backup copies, all of them publicly downloadable. A template install is how a folder gets into that state.
After activation, list the theme directory and the uploads folder for zip files, SQL, and backup suffixes. Remove them from the web root. The kit’s “help.html” does not need to be a URL on your company domain.
Child themes are the other piece of litter, in a kinder sense. Edit the child, not the parent, or the next update deletes the week you spent. If the template has no child theme and tells you to edit the parent, believe that you will lose the edits.
Budget the child theme as part of adopting the template. It is not a developer luxury. It is how the homepage survives an update.
The build, once a template has passed the deep-URL test, is WordPress development. Bringing a kit across the line is still development. It is not a weekend of clicking Import.
If the kit fails the test, paying for a skin on top of it will not create the product URL the kit couldn’t emit. Start from the URL list. Let the template compete for the job of printing it.
Most demos lose that competition, including the free ones with the nicest homepage.
Questions a template demo hides
Are free WordPress templates enough for a catalogue?
Sometimes, if a deep product URL can hold a real part number, specifications in text, and a form that lands in your inbox. The demo homepage is the wrong test. A URL that is not linked from the hero is the right one.
What did a heavy template actually do?
One template shipped a 15 MB image in the first screen. Hundreds of product URLs failed Core Web Vitals. The server was fine. The targets are an LCP within 2.5 seconds, an INP of 200 milliseconds or less, and a CLS of 0.1 or less.
When is a one-page builder the wrong tool?
When each product needs its own URL. A single scroll fits one offer. It runs out at product seven. Use it for a campaign. Don’t use it as the catalogue unless it can emit a real product address.
What should be deleted after importing a kit?
The kit’s own photos, media over a megabyte that you did not choose, and zip or backup files left in the theme directory. On one site, 36 .backup files in the theme folder were publicly downloadable.