Skip to main content

Pre-Sales & Technical Answers

Frequently Asked Questions

Straightforward answers on how we scope projects, measure speed, structure CMS workflows and hand over code.

Project Scoping & Delivery Process

How engagements are planned, scoped and delivered from initial enquiry to launch.

What kind of businesses does Faster Pixel work with?

We work with marketing managers, founders, product leads and digital teams across Australia who need fast, accessible corporate websites, e-commerce storefronts, web applications or targeted frontend performance improvements.

Can we engage Faster Pixel for a single service—such as speed optimisation—without rebuilding our whole website?

Yes. Services such as Website Speed Optimisation, Core Web Vitals Improvements, Website Accessibility Improvements and Frontend Engineering can be scoped on your existing codebase after a short technical suitability review.

What do we need ready before requesting a proposal?

You do not need a 50-page specification. Sharing your current URL (if you have one), the main business goal, approximate page or feature scope and any target timeline is enough for an initial scoping conversation.

How do you handle project milestones and approvals?

Projects are broken into clear phases—discovery and architecture, design/wireframes (where applicable), staging engineering, quality assurance and launch cutover—so your stakeholders review working deliverables at each stage.

Website Speed & Core Web Vitals

How we measure, budget for and improve loading speed and responsiveness.

How do you measure website performance?

We evaluate both calibrated lab traces (network waterfalls, bundle composition, throttled mobile CPU/4G tests) and real-user field telemetry where available (such as Chrome UX Report / Search Console metrics for LCP, INP and CLS).

Do you guarantee specific PageSpeed Insights scores or #1 Google rankings?

No. Synthetic scores vary with third-party scripts and network conditions, and search rankings depend on many external competition and content factors outside any developer’s control. Instead, we agree on concrete engineering deliverables, asset budgets and verifiable technical improvements.

Why does mobile performance usually look worse than desktop?

Mobile tests simulate mid-range phone processors and higher-latency cellular connections. Heavy JavaScript bundles and oversized images that a desktop CPU masks quickly become noticeable bottlenecks on mobile hardware.

Design, SEO Foundations & Accessibility

How visual craft, technical SEO and inclusive usability work together.

Is technical SEO included when you build a new website?

Yes. Every website build includes clean semantic HTML, crawlable navigation, unique title and meta description fields, canonical tags, XML sitemap generation, `robots.txt` rules, eligible structured data and 301 redirect support during cutover.

Who writes the page copy and supplies photography?

We can structure content outlines, draft editorial copy for review or work directly with your internal marketing writers. All service claims, credentials, staff bios, case studies and licensed visual assets are confirmed and approved by your business prior to publication.

What accessibility standards guide your builds?

We design and engineer against WCAG 2.1 / 2.2 Level AA technical principles—including readable contrast ratios, semantic headings, labelled forms, keyboard operability and `prefers-reduced-motion` support. Formal legal advice remains the role of your legal counsel.

CMS, Ownership & Ongoing Maintenance

Account ownership, content editing workflows and post-launch care.

Will our business own the domain, hosting and source code?

Yes. We set up domains, hosting environments, analytics properties and CMS accounts in your organisation’s name, and hand over custom project source code in accordance with your engagement agreement.

Will our team be able to update pages and publish blog articles ourselves?

Yes—when routine self-service publishing is part of your workflow, we implement a structured CMS with clear field guardrails and provide editor documentation so non-technical staff can publish confidently.

What happens after our website launches?

Every launch includes post-cutover verification checks. Beyond launch, you can opt into a structured Website Maintenance and Support plan covering dependency updates, speed monitoring, backups and ongoing enhancements, or manage updates internally.

Still have a specific technical question?

Reach out via our enquiry form or browse individual service detail pages for service-specific FAQs.