What makes a good homepage hero section?

A strong homepage hero helps the right visitor understand the business and choose a next step quickly. Check for: Audience and value: The message says who the business helps and why it matters. Specificity: The wording is concrete enough to mean something. Proof and visuals: Images or evidence support the message instead of competing with it. Action: The primary call to action fits the visitor's likely next step. Readability: Text, contrast, reading order, and buttons or links remain accessible. Mobile performance: The section stays clear and fast on a small screen.

Why does my Lighthouse score change between tests?

Lighthouse runs in a controlled environment, but server response time, network conditions, outside services, and the timing of page features can still vary. Use a repeatable process: Test the same page, device type, location, and general conditions. Run a small set of tests and compare the middle result instead of choosing the best or worst score. Look for repeated findings, then check real-user performance data in the Chrome User Experience Report or Search Console before making a major decision. A changing score is not automatically a problem. Consistent patterns and real-user results are more useful than one isolated run.

How should I decide whether to remove a HubSpot script from my website?

Do not remove a script just because it may slow a page. First confirm what it does and what depends on it: Identify the script’s purpose and the person or vendor responsible for it. Check whether it supports consent, forms, analytics, attribution, automation, or another integration. Measure how much it affects performance instead of assuming it is the main problem. Test the change on a test page or in a preview and confirm the affected features still work. Remove it only when it is redundant or the responsible owner approves the change. This protects the business functions behind the script while still giving you a practical path to improve performance.

Should I avoid animation on my website?

No, but every animation should earn its place. Before keeping it, check that it: Guides attention, explains a change, or supports the message. Respects a visitor's reduced-motion preference. Does not block access to content or controls. Works well on mobile and with touch input. Does not create an avoidable performance problem. If the motion is only decorative and adds distraction or delay, simplify it or remove it.

How can I decide whether a website feature is worth keeping?

Use a simple decision process: Purpose: Identify the visitor or business goal the feature supports. Evidence: Check analytics, conversion behavior, feedback, or testing for signs that it helps. Usability: Confirm that it works clearly and accessibly across devices. Performance: Compare its value with the speed or distraction it adds. Maintenance: Consider the time, cost, and risk required to keep it working. Keep it when the value is clear, change it when the idea is useful but the execution creates friction, and remove it when the cost outweighs the evidence.

Websites

Planning, building and improving your website.

Search FAQs

Still can’t find what you are looking for? Try ChatGPT.

Page 4 of 5 (45 questions)

A strong homepage hero helps the right visitor understand the business and choose a next step quickly. Check for:

Audience and value: The message says who the business helps and why it matters.
Specificity: The wording is concrete enough to mean something.
Proof and visuals: Images or evidence support the message instead of competing with it.
Action: The primary call to action fits the visitor's likely next step.
Readability: Text, contrast, reading order, and buttons or links remain accessible.
Mobile performance: The section stays clear and fast on a small screen.

Open answer

It can, and the amount depends mostly on how much content your site needs and how much research is already complete. Planning may include researching real customer questions, writing concise answers, organizing pages around those needs, and creating useful internal links. Accurate structured data may also be added where the page and content qualify, but there is no special schema that automatically makes a page ready for answer engines. Doing this work during the build is usually more efficient than reorganizing the site after launch.

Open answer

No. The 0–100 Lighthouse performance score shown in PageSpeed Insights is a controlled test result, not a ranking factor by itself. Google uses real-world Core Web Vitals among its broader page-experience signals, so data from actual visits can matter even when a single test looks good or bad. Use the score to find performance problems, then evaluate those findings alongside real-user data, content quality, and search relevance. Google's Core Web Vitals guidance explains how the real-world metrics fit into search.

Open answer

No, WordPress is not bad for business websites. A well-built WordPress site can be fast, strategic, flexible, and effective. The problem starts when WordPress tools are used to add features without a clear reason, a performance plan, or a marketing strategy.

View Longer Answer

Lighthouse runs in a controlled environment, but server response time, network conditions, outside services, and the timing of page features can still vary. Use a repeatable process:

Test the same page, device type, location, and general conditions.
Run a small set of tests and compare the middle result instead of choosing the best or worst score.
Look for repeated findings, then check real-user performance data in the Chrome User Experience Report or Search Console before making a major decision.

A changing score is not automatically a problem. Consistent patterns and real-user results are more useful than one isolated run.

Open answer

“WordPress thinking” is Smithworks' shorthand for making website decisions around what a tool makes easy instead of what visitors and the business need. It can show up as unnecessary plugins, excessive animation, bloated page builders, decorative sections, or unclear messaging. The same mindset can affect a HubSpot site when modules, scripts, forms, animations, or integrations are added without a clear purpose. The platform is not the problem. Tool-first decisions are.

Open answer

You need both, but they answer different questions. Lab data comes from a controlled test and helps identify what may be slowing a page down. Field data summarizes how real Chrome users experienced the site. The Chrome User Experience Report uses a rolling 28-day window, and page-level data may be unavailable when a page is not public or does not have enough visits. Use lab data to investigate and test changes, then use field data to confirm whether the real experience improved over time. See the Chrome User Experience Report methodology for details.

Open answer

Do not remove a script just because it may slow a page. First confirm what it does and what depends on it:

Identify the script’s purpose and the person or vendor responsible for it.
Check whether it supports consent, forms, analytics, attribution, automation, or another integration.
Measure how much it affects performance instead of assuming it is the main problem.
Test the change on a test page or in a preview and confirm the affected features still work.
Remove it only when it is redundant or the responsible owner approves the change.

This protects the business functions behind the script while still giving you a practical path to improve performance.

Open answer

No, but every animation should earn its place. Before keeping it, check that it:

Guides attention, explains a change, or supports the message.
Respects a visitor's reduced-motion preference.
Does not block access to content or controls.
Works well on mobile and with touch input.
Does not create an avoidable performance problem.

If the motion is only decorative and adds distraction or delay, simplify it or remove it.

Open answer

Use a simple decision process:

Purpose: Identify the visitor or business goal the feature supports.
Evidence: Check analytics, conversion behavior, feedback, or testing for signs that it helps.
Usability: Confirm that it works clearly and accessibly across devices.
Performance: Compare its value with the speed or distraction it adds.
Maintenance: Consider the time, cost, and risk required to keep it working.

Keep it when the value is clear, change it when the idea is useful but the execution creates friction, and remove it when the cost outweighs the evidence.

Open answer

Showing 31–40 · Page 4 of 5

Questions per page

Be Found

Be Trusted

Be Chosen

Help the right buyers find, trust, and choose you.

Understand what deserves attention first.

Websites

Open your brief

Taking you to your brief

We could not find that brief

Websites

What makes a good homepage hero section?

Does planning content for search and answer engines add time to a website build?

Does a PageSpeed Insights score directly affect SEO?

Is WordPress bad for business websites?

Why does my Lighthouse score change between tests?

What does Smithworks mean by “WordPress thinking”?

Is lab data or field data more important for website performance?

How should I decide whether to remove a HubSpot script from my website?

Should I avoid animation on my website?

How can I decide whether a website feature is worth keeping?