Guillaume DucuingIntegrating a website means bringing a design to life. But despite modern tools, some mistakes crop up again and again. Here are 5 common pitfalls to avoid for a clean and effective integration.
The mistake: integrating only for desktop, then "breaking" what's already there to adapt for mobile. The result: CSS hacks, bugs, and wasted time.
The right approach: think "mobile-first" or, at the very least, integrate desktop & mobile in parallel. Use clear and logical breakpoints from the beginning, with a consistent grid system.
Even if you still want to start with desktop, before jumping fully into integration, look at how the responsive version is designed. This will give you clues about how to build the desktop version and possibly catch design mistakes (sometimes our designer friends make things that are too different between desktop and mobile, for example).
The mistake: loading unoptimized images, importing 4 Google Fonts, adding useless scripts... And boom: PageSpeed crashes.
What to do:
Source: unsplashThe mistake: overusing <div>s, neglecting semantic tags (<header>, <main>, <section>, etc.), forgetting alt attributes on images…
Best practice:
For building your HTML, I strongly advise against using AI—it’s the best way to end up with a structure that isn’t really yours and that you don’t fully grasp. I prefer using AI for JS functions or for debugging.
Source: unsplashThe mistake: inline styling, super-specific classes, no naming logic, no reusability.
What to do:
Personally, I use Tailwind + React components: clear structure and reduced CSS.
On some projects I also use SCSS.
The mistake: not checking the appearance on multiple browsers, screen sizes, or user interactions.
Testing is essential:
A good user test is often better than 50 lines of code.
Source: unsplashTo wrap up, I didn’t make it a full point, but if you’re delivering projects for clients, you absolutely need to provide a CMS so that they can be autonomous. In 2025, I can’t imagine delivering my web projects without a solution that lets my clients make their own changes — without needing a developer to edit the content.
If you’ve read my other articles, you know I recommend Prismic because I find it an easy, flexible, and powerful headless CMS. But form your own opinion by testing other solutions on the market like Contentful, Strapi, or Sanity, for example.
Comments
Log in to add a comment
Sign in with Google