OnWeb · Website and cloud engineering
Optimized from the architecture up, not just at delivery.
A site can win design awards and still be invisible to Google. An optimized site is one where URL structure, heading hierarchy, load speed and structured data were decided as part of the project, not adjusted after someone noticed traffic never came.
We work in English, Portuguese and Spanish. Headquarters in Belo Horizonte, Brazil.
01Overview
SEO-optimized websites
SEO-optimized website is not an adjective in a sales pitch, it is a concrete list of technical decisions made before launch: stable URL architecture, headings organized by hierarchy, lightweight image formats, JavaScript trimmed to what is needed, and schema applied in the template.
OnWeb, the engineering front of the Netlinks group, builds this kind of site with the SEO team inside the project from the keyword map onward, so every page is born pointed at a real search intent, not at an empty slot in the menu.
The difference between an ordinary site and an optimized one shows up in the PageSpeed report and in how fast Google can crawl each page, long before any content campaign starts running.
Worth stressing: optimization is not a synonym for a stripped-down site with no features. You can have animation, video and a large catalog and still load fast, as long as every asset loads only when needed, instead of all at once on the first visit.
- 200+
- companies served since 2017
- 97/99
- mobile/desktop PageSpeed of the SP Labor homepage
- 6,433
- images compressed from 4.0 GB to 1.4 GB in the SP Labor case
- 24h
- of project tracking in the App
02Definition
What makes a site technically optimized
A site can load fast on the developer's machine and be slow for the real visitor, on mobile data, on an average phone. Technical optimization closes that gap with concrete decisions:
- Organized structure: short, stable URLs, a clear heading hierarchy, a menu that reflects the keyword architecture.
- Real load speed: compressed images in modern formats, fonts served from your own domain, scripts trimmed to what is needed.
- Relevant content per page: each page written for a specific intent, with no duplication that confuses indexing.
- Genuinely responsive design: tested on real devices, not just resized in the browser window.
A site with beautiful design but none of these fundamentals may not be found on Google at all. That is the difference between looking ready and being ready for search.
03Scope
What goes into optimizing a new site
URL architecture
A stable, readable address, built to last without a redirect.
Measured performance
PageSpeed and Core Web Vitals checked before publishing.
Image compression
Modern format and reduced weight with no visible quality loss.
Structured data
Schema applied in the template, not bolted on by a plugin later.
Tested responsiveness
Verified on real devices, not only in a simulator.
Ongoing monitoring
Performance tracking after launch, visible in the App.
04Comparison
An ordinary site versus an optimized one, side by side
The difference is not in the design, it is in what holds the design up behind the screen.
| Ordinary site | Optimized site | |
|---|---|---|
| URL | Auto-generated, can change over time | Set in the architecture, stable from launch |
| Image | Uploaded at original size | Compressed and in a lightweight format |
| Schema | Missing or applied by a generic plugin | In the template, specific per page type |
| Monitoring | None after launch | Ongoing, visible in the App |
05Diagnosis
Where most sites lose speed
A site is rarely slow for just one reason. In most diagnoses, the problem spreads across a few predictable points:
- Uncompressed images, often uploaded at the original camera or stock-photo size, ten times bigger than what the screen needs.
- Fonts loaded from an external server, adding an extra connection before the text even appears.
- Non-essential third-party JavaScript, like a chat widget or a tracking pixel, loaded before the main content.
- No cache configured, forcing the server to recompute the same page on every visit.
Fixing these four points usually captures most of the available performance gain, before any more sophisticated optimization.
06Metrics
The metrics that define a site as optimized
- LCP
Largest visible element
Time until the main element of the page fully appears on screen.
- INP
Interaction response
Time between a click or tap and the site's visual response.
- CLS
Visual stability
How much the layout shifts while the page is still loading.
- TTFB
Server response
Time until the server starts sending the page's content.
07Applied
What this work produces in practice
In the SP Labor case, the technical audit that came with the optimization cut the sitemap from 383 to 20 files and compressed 6,433 images, from 4.0 GB to 1.4 GB. The result showed up in PageSpeed: 97 on mobile and 99 on desktop, on the site's homepage.
That kind of number only happens when optimization is a project decision, not an emergency fix after traffic already dropped.
08The deliverable
What you receive
Finished work, approved by you in the App and shipped. Not a report that only describes the problem.
Site with measured performance
PageSpeed checked before publishing.
Defined URL structure
A stable, documented address, with no risk of a future redirect.
Schema applied
Structured data per page type, in the code.
Monitoring report
Performance tracked in the App after launch.
Image compression
The entire visual catalog optimized before going live.
09Who leads
Who leads your project
The three of them own the process and manage the team on every account. No senior who shows up at kickoff and disappears: they sign off on the plan, review the work and talk to your team.
Digo Garcia
Founder and CAIO
Over 20 years in digital. Built and scaled Letras.mus.br, then worked at Méliuz and in the joint venture with Globo.com. Owns AI, technical SEO and engineering inside every project.
Letras.mus.br · Méliuz · Globo.com
André Mousinho
Chief SEO Officer
Comes from Rock Content, Tray/Locaweb and LWSA. Designs the keyword mapping, the content architecture and the GEO strategy that turns a brand into the answer.
Rock Content · Tray/Locaweb · LWSA
Gabriel Raposo
Chief Authority Officer
Comes from Ambev and Agibank. Owns link building, digital PR and the authority that holds up both rankings and citations inside AI answers.
Ambev · Agibank
And the team behind them: Nathália Barcala (cofounder and COO, governance), Roberto Murta (CTO), Marcelo Ligere (senior advisor, 30+ years, formerly Grupo Globo) and Alfred, the artificial intelligence that runs the day to day: delivery queue, reporting and 24/7 support on WhatsApp.
10Who it is for
Where this work pays off the most
Company with a slow site
The current site takes too long to load, and it already affects ranking on Google.
A new project with a launch date
Wants to be born optimized, instead of fixing things after publishing.
E-commerce with many images
A large catalog, where image weight is usually the biggest speed bottleneck.
A company that already lost ranking to slowness
Noticed a traffic drop and the technical diagnosis points to speed as the cause.
11Case studies
Results with a name, a number and a date
Real projects, with what was done and what changed. No generic charts and no promises of a position.
FAQ
Frequently asked questions
What is an SEO-optimized website?
It is a site built with organized structure, a stable URL, compressed images, structured data and measured load speed, decided as part of the project.
What is the difference between this page and website optimization?
This page focuses on building a new site that is already optimized from the architecture up. Improving a site that is already in production is covered in website optimization.
How long until I see results with an optimized site?
The technical speed gain shows up immediately after launch. The search ranking gain usually arrives in 30 to 60 days, as content goes into production.
Is the optimized site suitable for mobile devices?
Yes. Every project is tested on real devices, not just resized in the browser window.
Why does optimization matter from the start of the project?
Because fixing URL structure, schema or performance after launch costs more, both in development time and in ranking lost along the way.
How does Netlinks make sure the site stays optimized over time?
With ongoing performance monitoring, visible in the App, and website management available to keep the standard after launch.
Which metrics do you use to define whether a site is optimized?
Google's own Core Web Vitals: LCP, INP, CLS and server response time. All checked before publishing and monitored afterward.
Keep reading
Related services
Next step
Get a diagnosis of your case
Tell us what your company sells and to whom. One of the three looks at your scenario, points out what is holding organic back today and shows where we would start.
- A review of your site and your market, with no commitment
- An answer from a senior specialist within 24 business hours
- A direct conversation: what can be done, in what order and how deep
Prefer WhatsApp?
Chat directly with a Netlinks Expert on WhatsApp.
Rather talk now? WhatsApp is answered by the team, with Alfred covering the rest of the day.
Talk to an Expert
Fill out the form and we will get back to you within 24 business hours.