The studio builds its own house.
The site you are reading right now - a static company website in practice. No admin panel, no plugins, no compromises - prerendered and edited like code, every change through build and deploy. Four Lighthouse audits pushed to 100/100, technical audit: every subpage passes.
I edit the site
like code, not like a panel.
The starting point.
The cobbler with no shoes: a brochure site on WordPress with 12 plugins, a click-together builder and a theme updated once every six months. Every copy change put off for weeks. Every update a risk. No time to maintain my own site, because every hand was on client work.
That was codecollab.pl in 2025: an old site built on a click-together builder, slow, out of date, describing an offer from two years earlier.
After the rebuild.
A statically prerendered site. Zero plugins, zero panel, zero themes to update. Edited like code - change the files, build, deploy. No clicking through a panel, no risk that the next plugin takes the site down.
That is codecollab.pl in 2026: the site keeps up with the business, not with the panel. A new case study? 30 minutes from idea to live. A change to the offer copy? 5 minutes.
The whole site,
top to bottom.
A screenshot from production - desktop, 6 June 2026. The full page top to bottom, or open codecollab.pl in a new tab.
Four audits,
four hundreds.
Performance 100, Accessibility 100, Best Practices 100, SEO 100. Plus a technical audit: every subpage passes on every check.
Measured: Chrome DevTools Lighthouse, 6 June 2026, 14:00.
What exactly
went into production.
- I
Architecture with no panel
Main pages (Home · About · Case studies · Free diagnosis · Contact), service pages, case studies and helper pages - all statically prerendered, the browser gets finished HTML on the first shot. Since launch the site has grown by more service pages and blog articles - every new page enters the same standard with no extra work.
- II
Measurement layer
Google Tag Manager and GA4 - ready for campaigns and for measuring leads honestly. The "form submitted" event as a tracked conversion.
- III
GDPR compliance
Consent banner and consent management, privacy policy, cookie policy. Analytics loads only after consent is given - no dark patterns.
- IV
On-page SEO + the 2026 standard for AI
Title, description, canonical and OG on every page, Schema.org (Organization, Person, FAQPage, Article).
robots.txtwith an explicit allow for AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended).llms.txtandllms-full.txtwith the full page content for LLMs. - V
Contact form with anti-spam
A form endpoint with a honeypot (a trap for bots) and a proof-of-work challenge (invisible to the user, impassable for a bot). Every lead lands in the inbox in real time.
- VI
Accessibility (A11y) at 100
AA colour contrast, semantic HTML, aria-label on every interactive element, a focus state on every link and button, keyboard covers navigation in full. A screen reader goes through the site without errors.
Before
you write.
What does "a site with no admin panel" mean?
codecollab.pl has no admin panel (the WordPress or Webflow kind). Content - copy, case studies, policies, meta tags - is edited like code: change the files, build, deploy. The result: faster iterations, no panel to maintain, no plugins to update and patch for security holes.
Is this model right for my company?
It fits if you change content once a week or less often and you do not need several non-technical people editing the site from a panel. Ideal for studios, freelancers and one-person B2B companies. I do not recommend it for online stores (a product panel is needed) or for publishers (daily publishing).
What Lighthouse score does this site reach?
Four Lighthouse audits at 100/100 - Performance, Accessibility, Best Practices, SEO. Technical audit: every subpage passes (title, meta, OG and canonical correct, alt on images, aria-label on CTAs, sitemap and robots.txt OK). Full page load ~50 ms on desktop.
Static site or WordPress - what should a company choose?
It depends on how often you change content and who edits it. A static site wins on speed, security and near-zero maintenance - ideal when content changes rarely. WordPress makes sense when several non-technical people have to edit the site from a panel. I build both models and fit the scope to the problem, not the other way round.
Would you build a site like this for me?
Yes - the "fast static site with no panel" model runs as a package. Getting in takes five questions and two minutes, and a fixed bid in writing comes back within 24 hours. Scope of 4-6 weeks, tailored to the project. B2B VAT invoice, EU VAT PL7372244067. Phone: +48 797 722 310.
Looking for this
for yourself?
The same standard of work - speed, accessibility, hard numbers - runs through three service tracks.
Want a site
that loads in half a second?
This kind of fast, static site with no panel and no plugins runs as a package - for studios, freelancers and B2B companies that want a site that is light, secure and maintenance-free. If your company needs a classic site with a panel instead, see how I approach web development. Send the scope - you get a fixed bid in writing within 24 hours.