Frequently Asked Questions - Websites

A website underperforms when it fails to help the business achieve the goal the site was built to support. That goal might be lead generation, stronger sales conversations, better search visibility, clearer service positioning, or a smoother path for existing customers.

Underperformance is not always obvious from the design alone. A site can look modern and still create confusion if the messaging is vague, the navigation is difficult, the calls-to-action are weak, or the content does not answer the questions buyers actually bring to the page.

The practical test is whether the website helps visitors understand, trust, and act. If it does not, the site is not doing its job yet.

Choose the platform that fits how your team will run the website after launch. Compare these factors:

• Day-to-day use: Decide whether you want the website and marketing tools in one platform or prefer assembling separate tools.
• Integrations: Confirm the CRM, commerce, analytics, and business systems each option must support.
• Maintenance: Identify who will manage hosting, security, updates, plugins, and technical issues.
• Customization: Document any design or functionality that standard themes and apps cannot handle.
• Total cost: Include subscriptions, hosting, extensions, development, and ongoing support.
• Marketer control: Test how easily your team can create, update, measure, and improve content.

HubSpot features vary by subscription. WordPress capabilities vary by host, theme, plugins, and development choices. Start with your requirements, not a blanket claim that one platform is better.

A hero banner is the large top section of a webpage, usually combining a headline, short supporting message, image or video, and a call-to-action. It is often the first major content section a visitor sees after the navigation.

Its job is not just to look impressive. A good hero banner should quickly communicate the page's main idea, help the visitor understand whether they are in the right place, and guide them toward the next step.

Because it sits at the top of the page, the hero banner often sets the tone for the whole visitor experience. If it is vague, crowded, or disconnected from the page goal, the rest of the page has to work harder.

A business website usually needs several connected skills, even when one person covers more than one role:

• Strategy and content: Goals, audience, messaging, offers, and page planning.
• User experience and design: Navigation, page structure, visual hierarchy, and accessible interaction.
• Building and publishing: Templates, reusable page sections, integrations, and tools marketers can maintain.
• Findability and quality: Search engine optimization (SEO), accessibility, performance, and testing.
• Delivery and measurement: Project management, analytics, launch planning, and ongoing improvement.

A small site may combine these responsibilities, while a larger or more specialized project may need several people.

For many small and medium business websites, plan on roughly 8 to 14 weeks from strategy through launch. A focused template-based site may take 3 to 6 weeks, while a rebuild with SEO migration work, custom features, ecommerce, or complex integrations can take 16 weeks or longer. Those are planning ranges, not promises: content readiness, stakeholder approvals, page count, migration risk, and testing can move the schedule quickly. Ask for a timeline tied to clear phases and assumptions before you treat any launch date as firm.

Look for problems in three areas:

• Business: Few qualified form submissions, repeated sales questions the site should answer, or calls to action that visitors overlook.
• Search: Declining organic traffic, important pages that are difficult to find, or broken links.
• Usability: Slow pages, confusing navigation, weak engagement, or a high bounce rate on pages where visitors should continue or take action.

Bounce rate needs context because a visitor may leave after getting exactly what the page promised. The clearest warning is a pattern of friction that keeps the website from helping visitors and supporting your business goals.

WordPress may have a lower starting software cost, but that does not tell you the total cost of running the website. Compare the same cost categories for both options:

• Platform subscriptions and user seats
• Hosting, backups, security, and monitoring
• Themes, plugins, apps, and integrations
• Maintenance, updates, and technical support
• Design, development, and future changes
• Marketing, analytics, and CRM tools needed around the website

Review current HubSpot Content Hub options. If you are considering WordPress.com, review its current plans. For a self-hosted WordPress site, get current costs from the host, plugin vendors, and people who will build and maintain it. The less expensive choice is the one with the better total cost for your team—not necessarily the lower advertised price.

Not exactly. A hero image is usually the visual asset used in the top section of the page, while a hero banner or hero section includes the full experience around that visual.

That experience may include the headline, subheadline, call-to-action, layout, background treatment, supporting proof, and strategic message. The image is only one part of the section.

This distinction matters because a strong hero section is not created by choosing a good-looking image alone. The image, message, and next step need to work together.

Web design usually focuses on the visual and experiential side of a website. That includes layout, typography, color, imagery, hierarchy, navigation, and how visitors understand the page.

Web development focuses on making the site function. That may include HTML, CSS, JavaScript, CMS templates, modules, forms, integrations, performance, security, and other technical requirements.

For a business website, both need to be guided by strategy. A beautiful site can still fail if the message is unclear, and a technically solid site can still underperform if the user experience does not support the buyer journey.

Website projects usually slow down when decisions, content, scope, or technical requirements remain unsettled. You can reduce the most common delays by planning for them early:

• Name one decision-maker and set approval deadlines.
• Set content deadlines before development depends on the copy.
• Control scope changes and document anything deferred to a later phase.
• Identify integrations and SEO migration needs before development begins.
• Protect a realistic quality-assurance window before launch.

A clear plan will not remove every surprise, but it keeps small questions from turning into schedule problems.