Skip to content
Tutorials Center
My learning

Topics

Lesson 37 of 37 ยท Projects and Practice

Practice, Troubleshooting and Next Steps

Practice exercises, a troubleshooting guide for common Wix and Webflow problems, choosing between the platforms and what to learn next, with runnable decision and diagnosis stand-ins.

You have now covered interactions, forms, stores, apps, SEO, performance, domains, publishing and accessibility, and built two projects. This final lesson gives you practice exercises, a field guide to problems you will really meet, a way to decide between the platforms, and a path for what to learn next.

Wix and Webflow are hosted and do not run on this site. The troubleshooting steps are general and based on how websites work; check each platform's current help center for product-specific details. The code samples are stand-ins for decision and diagnosis logic.

Practice exercises

Try these in your own free account. Each one fits in an hour or two.

  1. Hover card: build a project card that lifts and shows a "View case study" label on hover, and a tap-friendly version for touch (see Interaction Principles).
  2. Staggered reveal: make three feature cards fade up one after another when scrolled into view, with a reduced-motion fallback (Webflow Interactions and Timelines).
  3. Contact form: a three-field form with a honeypot, a success message and a notification to a shared inbox (Form Validation and Spam Protection).
  4. Price table: three products with two variants each; calculate the expected total for a two-item order to a faraway zone by hand, then match it with a test order (Shipping, Tax and Discount Math).
  5. SEO sweep: audit five pages for title, description, H1, alt text and indexing; fix everything you find (SEO Fundamentals).
  6. Redirect map: pretend you restructured the site; write ten old-to-new URL redirects with no chains (Structured Data, Sitemaps and Redirects).
  7. Speed budget: reduce a deliberately heavy page below 1.5 MB without changing its look (Performance, Images and Core Web Vitals).
  8. Accessibility pass: operate the whole site by keyboard only and fix three issues (Accessibility and Launch Checklist).

A troubleshooting method

When something breaks, avoid random changes. Use the same loop every time:

  1. Describe the problem precisely. What did you expect, what happened, on which page and device?
  2. Reproduce it. Does it happen in the published site, in preview, in a private window, on another browser?
  3. Isolate. Remove the newest change, disable the latest app or script, or duplicate the page and strip it down.
  4. Check the usual suspects (below).
  5. Fix one thing at a time and re-test.
  6. Record the cause and solution in your operations notes.

Common problems and causes

Symptom Likely causes What to check
Change not visible on the live site Not published; browser or CDN cache; editing the wrong domain Publish again; hard refresh or private window; check which domain you are viewing
Layout broken on mobile only Fixed widths, long unbroken text, large images, hidden overflow Inspect each breakpoint; use relative sizes and wrap settings
Form submits but no email Notification recipient wrong; spam folder; domain email authentication missing Test with another address; check spam; review SPF and DKIM (see Domains, DNS and SSL)
Custom domain shows an error or old page DNS records wrong or still propagating; old A record left; wrong primary domain Compare records with the dashboard values; wait for TTL; remove stale records
"Not secure" warning SSL not issued yet; mixed content (http images or scripts) Wait and re-check; change resources to https
Animation stutters Animating layout properties; too many elements; heavy images or video Switch to transform and opacity; reduce effects (Easing and Motion Performance)
Page is slow Large images, many apps and scripts, auto-playing video Compress; remove scripts; follow the budget
Checkout total looks wrong Tax setting (included versus added), shipping zone, discount stacking Place a test order and compare with your calculation
Page not in Google Indexing disabled, noindex tag, blocked by robots.txt, brand-new site Check settings, Search Console URL inspection, sitemap
Webhook not firing Wrong URL, plan lacks the feature, endpoint failing, trigger not matched Check logs on the receiver and the delivery history if available

A diagnosis helper

Real troubleshooting is judgment, but a decision table forces you to ask the right questions. This stand-in maps symptoms to the first things to check.

JS Stand-in: first checks by symptom

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Choosing between Wix and Webflow

Neither platform is "better"; they suit different people and jobs.

Factor Wix Webflow
Learning curve Gentler, template-led Steeper; needs understanding of HTML/CSS concepts (box model, flex, grid)
Design freedom Good; Studio adds more control Very high, close to hand-coded layouts
Content modeling (CMS) Capable collections, simple setup Powerful CMS with references and multi-references
Ecommerce Mature, many built-in business tools Flexible design, growing features; check limits
Extras Large App Market, built-in business suite (bookings, events) Strong integrations, clean code output, client Editor role
Code Velo for full-stack JavaScript Custom code, Data API, front-end code export
Typical user Small businesses, solo owners Designers, agencies, marketing teams

A decision stand-in makes the tradeoffs explicit; adjust the weights for your own project.

JS Stand-in: weighted platform choice

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Change the weights: if "Pixel-level design control" becomes 5 and "Speed to launch" becomes 2, the result flips. That is the point: the right answer depends on your priorities.

Migration and other options

Moving between platforms means rebuilding pages and moving content: export CMS data to CSV, copy images and rebuild layouts, recreate forms and integrations, and set 301 redirects from every old URL. For very large, data-heavy or heavily customized sites, a coded stack (a framework plus a headless CMS) or a dedicated ecommerce platform may be the better long-term fit.

What to learn next

  • HTML and CSS fundamentals: the best investment, since Webflow generates them and custom code uses them. See the HTML and CSS tutorials on this site.
  • JavaScript basics for custom behavior, embeds and Velo.
  • Design principles: typography, spacing, color, layout grids and visual hierarchy.
  • UX and content strategy: writing, information architecture and user research.
  • Analytics: Search Console and a privacy-aware analytics tool; learn to read the numbers and run small experiments.
  • Business skills if you freelance: scoping, contracts, pricing and client communication.

Start a real project: a site for a friend's business or a hobby is the fastest teacher.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the first step of a troubleshooting loop?

    You cannot fix what you cannot describe or reproduce; isolate before changing.
  2. 2. A change is missing on the live site. What do you check first?

    Unpublished edits and viewing the wrong domain or a cached copy are the commonest causes.
  3. 3. Webflow generally suits which user best?

    Webflow trades a steeper learning curve for fine control over layout and content structure.
  4. 4. Which is the best long-term learning investment for site builders?

    Understanding HTML and CSS helps you in either platform and with custom code.

Summary

  • Practice by building small, focused exercises and fixing them.
  • Troubleshoot methodically: describe, reproduce, isolate, check the usual suspects, fix one thing, record.
  • Choose between Wix and Webflow by your priorities: speed and built-in tools versus design and CMS control.
  • Keep learning HTML, CSS, JavaScript, design, UX and analytics, and build real projects.

Next: Back to the Wix and Webflow track