Scroll Top

How to Use Custom CSS on a Squarespace Site

Updated September 2026 · Written and maintained by the Progression Agency strategy team

The custom CSS panel is easy to find. What causes problems is what people write in it: rules targeting generated class names that change without warning, blanket overrides that alter unrelated pages, and appearance changes that break keyboard navigation. This covers what to try before writing any code, how to write rules that survive an update, the accessibility mistakes worth knowing, and the point at which more CSS is the wrong answer.

The short answerEvery rule you do not write is a rule that cannot break during an update. Check the built-in style settings first — most spacing, type and color changes are settings rather than code, and settings survive updates. And never remove focus outlines for appearance: it makes the site unusable by keyboard, and restyling the outline achieves the same look without the damage.

Progression Agency is based in New York City and works with clients across the United States. Squarespace’s interface, custom CSS panel, template structures and generated class names change over time — follow the current process in the product and in Squarespace’s own documentation rather than any third-party description, including this one. Nothing here is a substitute for testing on your own site.

Custom CSS, in short
Copying a snippet without reading it causes more site problems than any technical issue here: it solved somebody else’s problem on a different template.

How do you use custom CSS on a Squarespace site?

Through the built-in custom CSS panel, which applies your rules on top of the template’s own styles — and the whole skill is writing rules specific enough to work and general enough to survive an update.

The panel is easy to find. What causes problems is what people write in it: rules targeting generated class names that change without warning, and blanket overrides that break unrelated parts of the site.

The order to work in
Steps one and two remove most of the need for step four, which is the point: the best custom CSS is the rule you never had to write.

What should you try before writing any CSS?

Everything the built-in settings offer. Custom CSS that duplicates a setting is a maintenance liability with no benefit.

This is the single most useful discipline here: every rule you do not write is a rule that cannot break during an update.

Check style settings — Before coding. They survive updates..
Check section options — Before coding. Layouts cover a lot..
Weigh the maintenance — Before coding. Every rule is future work..
Question the template — Before coding. Fighting it is expensive..
Check responsive behavior — Before coding. You may break it..
Note why — Before coding. Or it never gets removed..

Check the site styles panel first

Most spacing, type and color changes are settings rather than code, and settings survive updates.

Check whether a section option does it

Layout variations frequently cover what people write CSS for.

Ask whether the change is worth the maintenance

Every custom rule is something to re-test after a platform update.

Consider whether the design should change instead

Fighting a template with code usually means the template is the wrong one.

Check it is not already handled responsively

Overriding something that adapts by design frequently breaks it on other screen sizes.

Keep a note of why each rule exists

Six months later nobody remembers, and unexplained CSS never gets removed.

What makes a custom CSS rule fragile?

Targeting auto-generated class names, relying on element position, over-using importance declarations, and writing rules with no responsive consideration.

Fragile rules do not fail immediately. They fail at the next platform update, usually unnoticed, and usually on a page nobody checks.

Fragile CSS and what to write instead
Fragile approachWhy it breaksMore durable approach
Auto-generated class namesThey change on rebuildTarget stable structural selectors
Positional selectors like nth-childContent order changesTarget by a stable attribute
Blanket element overridesAffects unrelated areasScope to a section or page
Importance declarations everywhereNothing can override anythingRaise specificity instead
Fixed pixel heightsContent length variesLet content set height
Desktop-only rulesBreaks on phonesWrite mobile behavior deliberately
Hiding elements with display noneStill loads; may hide needed contentRemove it properly
Copying a snippet without reading itUnknown side effectsUnderstand before pasting

The last row causes more site problems than any technical issue on this list. A snippet copied from a forum solved somebody else’s problem on a different template, and its side effects arrive later.

How do you make a rule apply to one page only?

By scoping it to that page’s own identifier rather than writing a global rule and hoping nothing else uses the same element.

Page-scoped rules are the difference between a change you can reason about and a change that quietly alters something on a page you had forgotten existed.

How should custom CSS handle mobile?

Deliberately, with the mobile behavior written rather than inherited — because a desktop rule applied everywhere is the commonest cause of a broken phone layout.

Most site traffic is mobile, so a rule that improves desktop and degrades mobile is a net loss even when it looks like an improvement.

Where custom CSS most often breaks mobile
Relative frequency, not measured values. Most site traffic is mobile, so a rule that improves desktop and degrades mobile is a net loss.

Write breakpoints deliberately

Rather than letting a desktop rule apply at every width.

Test at real device widths

Not by narrowing a browser window, which misses touch behavior.

Remember hover does not exist on touch

Anything revealed on hover is unavailable on a phone.

Watch touch target sizes

Small tap targets are a genuine usability failure, not a preference.

Check text remains legible

Reduced sizes and light colors fail faster on a phone in daylight.

Check nothing overflows horizontally

A page that scrolls sideways on mobile reads as broken.

What are the accessibility risks of custom CSS?

Removing focus outlines, reducing contrast, hiding content visually while leaving it in the document, and shrinking text below legible sizes.

Removing the focus outline is the most common and most damaging: it makes the site unusable by keyboard, and it is almost always done for appearance.

Accessibility mistakes in custom CSS
What people writeWhat it breaksWhat to do instead
Removing focus outlinesKeyboard navigation entirelyRestyle the outline, do not remove it
Lightening text for eleganceLegibility, especially outdoorsCheck the contrast ratio
Very small text sizesReadability for many usersKeep body text at a legible size
Color-only state changesAnybody with color vision differencesAdd a shape or text cue
Hiding content visually onlyScreen readers still announce itRemove or hide properly
Disabling zoomAnybody who needs to enlargeNever disable it
Fixed overlays covering contentSmall screens especiallyTest at real sizes
Motion without a preference checkPeople sensitive to motionRespect reduced-motion

The reduced-motion row is easy to satisfy and frequently overlooked: browsers expose a preference for reduced motion, and honoring it takes one media query.

Does custom CSS affect site speed or SEO?

A small amount of CSS is negligible. Large accumulated stylesheets and rules that cause layout shifts are not.

The bigger SEO risk is not the CSS itself but what people use it for — hiding content, which search engines treat differently from content that is genuinely visible.

How should you organize custom CSS so it stays maintainable?

Group it by page or component, comment every block with what it does and why, and delete rules when the reason for them goes away.

An unmaintained custom CSS panel becomes a file nobody dares to touch, which then constrains every future change to the site.

Comment every block — Organize. What, where, and why..
Group by page — Organize. Not chronologically appended..
Date additions — Organize. Some history helps..
Delete dead rules — Organize. Deleted CSS cannot break..
Keep a copy elsewhere — Organize. Not only in one panel..
Re-test after updates — Organize. Especially generated selectors..

Comment every block

What it does, which page, and why. Future you will not remember.

Group by page or component

Rather than appending each new rule to the bottom.

Date significant additions

So the accumulation has some history.

Remove rules when their reason ends

Deleted CSS cannot break anything.

Keep a copy outside the platform

So the work is not only in one panel.

Re-test after platform updates

Especially anything targeting generated class names.

When should you stop using custom CSS and change something else?

When the amount of code needed to make a template behave is larger than the work of choosing a template that behaves that way already.

Fighting a template is the most common expensive mistake here, and it compounds: every subsequent change has to work around the accumulated overrides.

Should you write this rule at all?
Only the second entry is comfortably worth writing. Everything in the lower half will need re-testing at every platform update, indefinitely.
Signs you are fighting the template rather than styling it
SignWhat it usually meansBetter response
Rules keep breaking after updatesTargeting unstable selectorsReconsider the approach
Importance declarations everywhereFighting the template’s own stylesChange template or design
Hundreds of lines for one sectionThe section is wrong for the needUse a different section
Nobody will touch the CSS panelIt has become unmaintainableRewrite it, commented
Mobile needs its own full rulesetThe design does not adaptRethink the design
Every new page needs new rulesNo reusable systemBuild components, not one-offs
Changes take longer than they shouldAccumulated overridesAudit and delete
Fear of updating the platformFragile customizationStabilize it before updating

The bottom row is the real cost. Customization that makes a business afraid to update its own platform is a security and maintenance problem rather than a design one.

What should you do before every platform update?

Note what you have customized, take a copy of the CSS, and check the customized pages afterwards — particularly anything targeting generated class names.

Ten minutes of checking after an update catches problems that otherwise sit unnoticed for months on pages nobody visits daily.

What can custom CSS not fix?

Anything that is a content or structure problem: unclear copy, a page that does not say what the business does, or a site organized around the owner rather than the visitor.

This is worth stating plainly because a great deal of custom CSS is written in pursuit of a conversion improvement that styling cannot deliver.

Problems people try to solve with CSS, and what actually solves them
ProblemCSS responseWhat actually fixes it
Visitors leave immediatelyRestyle the heroSay what you do, for whom
Nobody inquiresMake the button brighterClarify the offer and the next step
Page feels clutteredReduce spacingRemove content nobody needs
Site looks datedChange fonts and colorsFrequently a structure problem
Mobile is awkwardAdd mobile overridesSimplify what is on the page
Page is slowNothing CSS can doImages, scripts and hosting
Not found in searchNothing CSS can doContent, structure, technical fixes
Content is hard to scanRestyle headingsWrite shorter sections with real headings

Only the last row is even partly a styling problem, and the fix there is as much editorial as visual. CSS makes a page look the way you intend; it cannot make the page say something it does not say.

Canva: magic eraser, seamless carousels, custom fonts, and Snappa

Design-tool questions arrive constantly alongside site-customization ones, because the same person is usually doing both. These are the ones that come up most.

Magic eraser in Canva

Magic eraser Canva offers is a Pro feature, so Canva Pro magic eraser access is required — which is the answer to most of the confusion. Where to find magic eraser in Canva: open an image, choose Edit, then the retouch tools. How to use magic eraser well is a matter of brushing slightly beyond the object rather than precisely around it, because the fill works from surrounding pixels.

Seamless Instagram carousels in Canva

How to make a continuous Instagram post on Canva means designing one wide canvas and slicing it, rather than designing separate panels. How to make a continuous Instagram post Canva handles well: set a canvas that is a multiple of the post width, design across it, then export as separate frames. A seamless carousel Instagram users can swipe without a visible join needs the slice boundaries planned before the design, not after. Seamless multi post Instagram layouts and a seamless Instagram carousel Canva produces are the same technique under different names.

Uploading fonts to Canva

Canva fonts upload is a Pro feature under Brand Kit. How to upload fonts to Canva: Brand Kit, then Fonts, then upload the file. Can you upload fonts to Canva on a free account — no, which is the answer people are usually looking for. Canva font upload accepts common desktop formats, and the license you hold for the font still governs commercial use once it is there; upload fonts to Canva you actually have rights to.

Canva versus Snappa

What is Snappa: a lighter graphics tool aimed at social and ad creative. The Snappa app covers a narrower set of use cases with less depth than Canva and, for some people, less friction because of it. Canva vs Snappa comes down to breadth against simplicity — if you need brand kits, video and document work, the answer is Canva; if you need social graphics quickly and nothing else, Snappa is defensible.

Site held together by custom CSS nobody wants to touch?

We work with clients across the United States on websites that stay maintainable — which sometimes means removing accumulated overrides rather than adding more, and occasionally means saying the template is the problem.

Talk to Progression Agency

Video: web and marketing practice

A general library on marketing practice. The CSS material is written out in full above.

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Frequently asked questions

Where can I find squarespace css codes that actually work?
In Squarespace’s own developer documentation and by inspecting your site’s live classes. Squarespace css codes copied from blog posts frequently target class names from an older version, which is why a snippet does nothing — inspect the element on your own site and write the selector against what is actually there.
How do I squarespace edit css on a live site safely?
Work in a duplicate or use a staging trick, because there is no preview isolation. To squarespace edit css you open Design, then Custom CSS, and changes apply site-wide immediately on save. Copy the existing block into a text file before you start so you can revert.
Where is the squarespace css editor located?
Design, then Custom CSS, in both 7.0 and 7.1. The squarespace css editor is a single site-wide panel rather than a per-page one, which is why targeting individual pages requires a collection or page ID selector rather than a separate stylesheet.
Can I edit css squarespace applies to only one page?
Yes, by scoping the rule to that page’s ID. To edit css squarespace serves on a single page, use the body class Squarespace adds — `#collection-xxxxx` or `.collection-xxxxx` — as a prefix. Without that prefix every rule you write applies everywhere.
Is the css editor squarespace provides the same on every plan?
Custom CSS requires a paid plan, and the panel is identical across those. The css editor squarespace includes is not available on the trial or the lowest tier in some regions, so check your plan before building a design that depends on it.
Where is custom css in squarespace 7.1 specifically?
Under Website, then Website Tools, then Custom CSS on current builds. Where is custom css in squarespace has moved more than once, which is why older tutorials point at menus that no longer exist. Search ‘custom CSS’ in the admin search bar if the path has changed again.
How to add custom css in squarespace without breaking the theme?
Add rules, do not override the theme’s base styles wholesale. How to add custom css in squarespace safely means targeting specific elements rather than broad tags: restyling every `h2` on the site will change pages you have not looked at. Scope narrowly and check on mobile.
Where is the custom CSS panel in Squarespace?
In the site’s design settings, under custom CSS. Adding custom CSS Squarespace-side applies your rules on top of the template’s own styles, which is why specificity and scoping decide whether a rule works.
How do you add custom CSS to a Squarespace site?
Through the built-in custom CSS panel, where your rules are applied on top of the template’s own styles.
What should I try before writing custom CSS?
Everything the built-in style settings and section options offer. Custom CSS duplicating a setting is a maintenance liability with no benefit.
Why does that matter so much?
Because settings survive platform updates and custom rules may not. Every rule you do not write is a rule that cannot break later.
What makes a CSS rule fragile?
Targeting auto-generated class names, positional selectors, blanket element overrides, importance declarations everywhere, and rules written without responsive consideration.
Why are generated class names a problem?
Because they can change when the platform rebuilds its stylesheets, and the rule then silently stops applying — usually noticed months later.
How do I make a rule apply to one page only?
Scope it to that page’s own identifier rather than writing a global rule and hoping nothing else uses the same element.
What is wrong with importance declarations?
Used everywhere, they leave nothing able to override anything, including your own later rules. Raising specificity is usually the better answer.
Should I copy CSS snippets from forums?
Only after reading and understanding them. A snippet solved somebody else’s problem on a different template, and its side effects arrive later.
How should custom CSS handle mobile?
Deliberately. Write the mobile behavior rather than letting a desktop rule apply at every width, which is the commonest cause of a broken phone layout.
How should I test mobile?
At real device widths on a real device, not by narrowing a browser window — which misses touch behavior entirely.
What about hover effects?
Hover does not exist on a touch screen. Anything revealed only on hover is unavailable to most of your visitors.
What is the most damaging accessibility mistake?
Removing focus outlines. It makes the site unusable by keyboard, and it is almost always done for appearance. Restyle the outline instead of removing it.
Can I make text lighter for a more elegant look?
Only if it still meets contrast requirements. Light text fails first on a phone in daylight, which is a common real viewing condition.
Is hiding content with CSS a problem?
It can be. Visually hidden content is still in the document and still announced by screen readers, and hiding content is treated differently by search engines than genuinely visible content.
Should I ever disable zoom?
No. Disabling zoom removes an essential capability for anybody who needs to enlarge text, and there is no design justification that outweighs it.
What about animation and motion?
Honor the reduced-motion preference. Browsers expose it, respecting it takes one media query, and it matters for people sensitive to motion.
Does custom CSS hurt site speed?
A small amount is negligible. Large accumulated stylesheets and rules causing layout shifts are not, and the accumulation is the usual problem.
Does custom CSS affect SEO?
Not directly in most cases. The risk is what people use it for — particularly hiding content, which is treated differently from content that is genuinely visible.
How should I organize custom CSS?
Group it by page or component, comment every block with what it does and why, date significant additions, and delete rules when their reason ends.
Why comment everything?
Because six months later nobody remembers why a rule exists, and unexplained CSS never gets removed — it just accumulates.
Should I keep a copy outside the platform?
Yes. Work that exists only in one panel is work you can lose, and a copy makes comparison after an update straightforward.
What should I do before a platform update?
Note what you have customized, take a copy of the CSS, and check the customized pages afterwards — particularly anything targeting generated class names.
How do I know I am fighting the template?
Rules breaking after every update, importance declarations everywhere, hundreds of lines for one section, or nobody being willing to touch the CSS panel.
What should I do about that?
Reconsider the template or the design. Fighting a template compounds, because every subsequent change has to work around the accumulated overrides.
What is the real cost of fragile customization?
A business afraid to update its own platform. That is a security and maintenance problem rather than a design one.
Should every new page need new CSS?
No. If it does, you have one-off rules rather than a reusable system, and the maintenance cost grows with every page.
Is it ever right to remove custom CSS rather than add more?
Frequently. An audit that deletes rules whose reason has ended makes every future change faster and lower-risk.
Where should I verify the current process?
Squarespace’s own documentation and the product itself, since interfaces and structures change and third-party descriptions date quickly.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. Google Ads: location targeting settings
  24. Google Ads: about negative keywords
  25. Google Ads: about Quality Score
  26. Google Ads: importing offline conversions
  27. Google Ads: about Smart Bidding
  28. Google Ads: about Performance Max
  29. Google Local Services Ads: eligibility and screening
  30. Google Ads: keyword match types
  31. Google Analytics 4: about conversions
  32. Google Analytics 4: attribution models
  33. US Census Bureau QuickFacts: New Jersey
  34. US Census Bureau: American Community Survey
  35. US Census: Statistics of US Businesses
  36. Bureau of Labor Statistics: New Jersey data
  37. BLS: Occupational Employment and Wage Statistics
  38. NJ Department of Labor: labor market information
  39. New Jersey Business Action Center
  40. US Small Business Administration: New Jersey district
  41. USA.gov: business resources
  42. web.dev: Core Web Vitals explained
  43. web.dev: Largest Contentful Paint
  44. web.dev: Cumulative Layout Shift
  45. web.dev: Interaction to Next Paint
  46. Google PageSpeed Insights
  47. Google Rich Results Test
  48. Google Search Console
  49. W3C Markup Validation Service
  50. Schema.org: LocalBusiness type
  51. Schema.org: Service type
  52. Schema.org: FAQPage type
  53. Schema.org: HowTo type
  54. W3C: WCAG 2.2 quick reference
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek
  232. MDN — CSS specificity
  233. MDN — prefers-reduced-motion
  234. MDN — the focus-visible pseudo-class
  235. W3C — Understanding focus visible
  236. W3C — Understanding reflow
  237. web.dev — cumulative layout shift

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Our website uses cookies from third party services to improve your browsing experience. Read more about this and how you can control cookies by clicking "Privacy Preferences".
Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Privacy Policy
You have read and agreed to our privacy policy
Required