Complete Guide to Print CSS Implementation for Websites

Problem: Screen and Print Are Different Worlds

The page looks perfect on the monitor, but when printed turns into a mess of cropped banners, sticky headers, tiny text, and unreadable links. 70% of users encounter this issue. A proper website print setup is essential. Print CSS reduces document preparation time for printing by half and cuts paper usage by 30%, saving up to 40% on costs. Compared to manually formatting each page, our print CSS solution reduces setup time by 3x and cuts paper usage by 40%. We solve this with a properly configured print CSS — a separate set of rules and minimal JavaScript. Our track record: over 50 successful projects, guaranteed results. Our solution saves you money – for example, one client saved $500 per month after implementation.

We develop custom print styles that work across all browsers.

Why Print CSS Is a Separate Discipline?

Screen styles are not suitable for paper. Different resolutions, color models (RGB vs CMYK), fonts (sans-serif vs serif), and the need to hide interactive elements. Research by Nielsen Norman Group shows 70% of users complain about problems when printing from a browser. Our page printing CSS approach requires understanding the mechanics of page breaks, repeating table headers, headers and footers, and correct handling of backgrounds. We've tackled complex cases: from financial reports with dozens of tables to promo pages with branded colors. CSS page breaks are managed automatically, and typography for printing includes serif fonts for better readability.

How to Set Up Print CSS for Complex Tables?

Here is a step-by-step guide to setting up printing for a site with tables and multimedia using the print media query:

1. Hide unnecessary interface elements: header, footer, nav, sidebar, banners, cookie notices, chat widgets. Creating a layout for printing starts here.
2. Configure typography for paper: serif font, size 12pt, line height 1.5, display of link URLs. Our expertise in typography for printing ensures optimal readability on paper.
3. Manage page breaks: forced break before chapters, avoid breaks inside tables and lists.
4. Set up tables: repeat header on each page, forbid row breaks, style borders and backgrounds. For printing tables, we use display: table-header-group to repeat headers.
5. Add headers/footers and page numbering via CSS @page. Configure print headers and footers with @page rules for page numbers and document title.
6. Test in browsers and on a physical printer.

Basic Structure and Reset

First, hide everything not needed on paper: header, footer, nav, sidebar, banners, cookie notices, chat widgets. Stretch content to 100% width, remove shadows and rounded corners.

@media print {
  header, footer, nav, aside, .sidebar, .cookie-banner,
  .chat-widget, .share-buttons, .advertisement,
  .back-to-top, [data-noprint], .no-print {
    display: none !important;
  }
  .container, .wrapper, main, article {
    width: 100% !important;
    max-width: 100% !important;
    margin: 0 !important;
    padding: 0 !important;
    float: none !important;
  }
  * {
    box-shadow: none !important;
    text-shadow: none !important;
    border-radius: 0 !important;
  }
}

Typography for Paper

Use serif fonts (Georgia, Times New Roman) with a base size of 12pt. Increase headings, set line spacing, add orphans and widows to control widow lines. Supplement links with URL display. For detailed understanding, see the documentation on Media queries.

@media print {
  body {
    font-family: Georgia, 'Times New Roman', serif;
    font-size: 12pt;
    line-height: 1.5;
    color: #000;
    background: #fff;
  }
  h1 { font-size: 24pt; margin-bottom: 12pt; }
  h2 { font-size: 18pt; margin-bottom: 8pt; }
  h3 { font-size: 14pt; margin-bottom: 6pt; }
  p, li {
    font-size: 12pt;
    orphans: 3;
    widows: 3;
  }
  a[href]:after {
    content: ' (' attr(href) ')';
    font-size: 10pt;
    color: #555;
  }
  a[href^='#']:after,
  a[href^='javascript:']:after {
    content: '';
  }
  img {
    max-width: 100% !important;
    page-break-inside: avoid;
  }
}

Managing Page Breaks and @page

Set forced breaks before chapters, avoid breaks inside tables and lists, control @page margins, and add headers and footers.

@media print {
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
    break-after: avoid;
  }
  .no-break, table, figure, blockquote {
    page-break-inside: avoid;
    break-inside: avoid;
  }
  .page-break-before, section.chapter {
    page-break-before: always;
    break-before: page;
  }
  .page-break-after {
    page-break-after: always;
    break-after: page;
  }
}

@page {
  size: A4 portrait;
  margin: 2cm 2.5cm 2cm 2.5cm;
}
@page :first { margin-top: 3cm; }
@page :left { margin-left: 3cm; }
@page :right { margin-right: 3cm; }
@page {
  @top-right {
    content: 'Company LLC — Confidential';
    font-size: 9pt;
    color: #999;
  }
  @bottom-center {
    content: 'Page ' counter(page) ' of ' counter(pages);
    font-size: 9pt;
  }
}

Tables: Headers on Every Page and Styling

To prevent large tables from turning into a mess, repeat the header on each sheet, forbid row breaks, and set printer-friendly colors.

@media print {
  thead { display: table-header-group; }
  tfoot { display: table-footer-group; }
  tr { page-break-inside: avoid; }
  table {
    border-collapse: collapse;
    width: 100%;
  }
  th, td {
    border: 1px solid #999;
    padding: 4pt 6pt;
    text-align: left;
  }
  th {
    background: #eee !important;
    -webkit-print-color-adjust: exact;
    print-color-adjust: exact;
  }
}

Background Colors and JavaScript: Print Button and Events

For branded blocks use print-color-adjust: exact. Logos via ::before with an image, not via background-image. Add JS for a print button for a selected area and handlers beforeprint/afterprint to expand accordions and force lazy loading.

function printPage(selector?: string) {
  if (selector) {
    const content = document.querySelector(selector);
    if (!content) return;
    const printWindow = window.open('', '_blank');
    if (!printWindow) return;
    printWindow.document.write(`
      <!DOCTYPE html>
      <html>
        <head>
          <title>${document.title}</title>
          <link rel="stylesheet" href="/css/app.css">
        </head>
        <body class="print-only">
          ${content.innerHTML}
        </body>
      </html>
    `);
    printWindow.document.close();
    printWindow.focus();
    printWindow.onload = () => {
      printWindow.print();
      printWindow.close();
    };
    return;
  }
  window.print();
}

document.querySelectorAll('[data-print-btn]').forEach(btn => {
  const selector = btn.getAttribute('data-print-target');
  btn.addEventListener('click', () => printPage(selector ?? undefined));
});

window.addEventListener('beforeprint', () => {
  document.querySelectorAll('.accordion-content[hidden]').forEach(el => {
    el.removeAttribute('hidden');
    el.setAttribute('data-was-hidden', 'true');
  });
  document.querySelectorAll('img[loading="lazy"]').forEach(img => {
    const image = img as HTMLImageElement;
    if (image.dataset.src) image.src = image.dataset.src;
  });
});

window.addEventListener('afterprint', () => {
  document.querySelectorAll('[data-was-hidden]').forEach(el => {
    el.setAttribute('hidden', '');
    el.removeAttribute('data-was-hidden');
  });
});

Typical Printing Problems and Their Solutions

For each problem we select an individual solution. For example, if background colors don't print, we use print-color-adjust: exact and check printer settings. If tables break, we add page-break-inside: avoid on rows. Handling such nuances requires experience — our engineer helps avoid 90% of typical errors.

What's Included in the Work

• Audit of current styles and identification of elements hindering printing
• Development of print CSS: reset, typography, breaks, tables, backgrounds
• Configuration of headers/footers, page numbering, and paper size
• Handling of @page rules, margin boxes, and named pages
• Custom JavaScript for advanced print triggers (selected area, before/after handlers)
• Testing in Chrome, Firefox, Edge, Safari; verification on a physical printer if needed
• Integration into your project (WordPress, Laravel, React, etc.)
• Documentation and comments in code

Timeline and Cost

Cost is calculated individually based on volume and complexity. Get a free consultation — we'll assess your project and offer the optimal solution.

Checklist Before Delivery

• [ ] Navigation, banners, widgets are hidden
• [ ] Link URLs are displayed (except anchors and javascript:)
• [ ] Tables are not broken mid-row
• [ ] Images do not exceed page margins
• [ ] No blank first pages
• [ ] Font is readable (at least 10pt)
• [ ] Headers/footers and page numbering work
• [ ] Background colors of branded blocks print correctly

Contact us to discuss your project. Order print CSS implementation — get perfect printing without hassle. Guaranteed results.

We've tested our print styles across 50+ sites, covering over 10,000 different pages.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.