Remove Best Practices Remove Magazine Remove Strategy Remove Testing Tools
article thumbnail

Refactoring CSS: Strategy, Regression Testing And Maintenance (Part 2)

Smashing Magazine

Refactoring CSS: Strategy, Regression Testing And Maintenance (Part 2). Refactoring CSS: Strategy, Regression Testing And Maintenance (Part 2). Finally, the team needs to agree on the refactoring strategy and regression testing method. Incremental Refactoring Strategy. Adrian Bece.

Strategy 132
article thumbnail

Front-End Performance Checklist 2019 [PDF, Apple Pages, MS Word]

Smashing Magazine

It might be tempting to get into quick "low-hanging-fruits"-optimizations early on — and eventually it might be a good strategy for quick wins — but it will be very hard to keep performance a priority without planning and setting realistic, company-tailored performance goals. Set up "clean" and "customer" profiles for testing.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Front-End Performance Checklist 2021

Smashing Magazine

In many organizations, front-end developers know exactly what common underlying problems are and what strategies should be used to fix them. Performance Budgets, Pragmatically shows you a strategy to achieve that. There are many tools allowing you to achieve that: SiteSpeed.io Establish a performance culture. Large preview ).

article thumbnail

Front-End Performance Checklist 2020 [PDF, Apple Pages, MS Word]

Smashing Magazine

It might be tempting to get into quick "low-hanging-fruits"-optimizations early on — and it might be a good strategy for quick wins — but it will be very hard to keep performance a priority without planning and setting realistic, company-tailored performance goals. Lighthouse , a performance auditing tool integrated into DevTools.

article thumbnail

HTTP/3: Practical Deployment Options (Part 3)

Smashing Magazine

You would, however, be hard-pressed even today to find a good article that details the nuanced best practices. This is because, as I stated in the introduction to part 1 , much of the early HTTP/2 content was overly optimistic about how well it would work in practice, and some of it, quite frankly, had major mistakes and bad advice.

Network 104