
Jump Start Web Performance
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
Despite working on the web every day, few developers have a good word to say about the monster they've created. Achingly slow sites with annoying overlays, cookie agreements, instant notifications, and obtrusive ads litter the web landscape.
While there may be some excuses for complex web applications, there's little justification for sluggish content-based and ecommerce sites. People are notoriously impatient, and an unresponsive site receives fewer visitors and conversions.
This practical, short book provides advice, tips, and best practice for improving website performance, ranging from quick, five-minute configuration changes to major website overhauls. We primarily concentrate on front-end activities and server configurations to optimize the code delivered to a browser. Some back-end tips are provided, but this is often specific to your application, framework, database, and usage patterns. Server-side performance can often be improved with additional or more powerful computing resources.
Ideally, everyone involved in a project would consider performance from the start. Somewhat understandably, that rarely occurs, because no one can appreciate the speed of a website or application before it's been created. Many of the tips contained in this book can therefore be applied after your project has been delivered.
More details
Person
Craig is a freelance developer, author, and speaker who never shuts up about the web. He started coding in the 1980s when applications had to squeeze into a few kilobytes of RAM. His passion for the Web was ignited in the mid 1990s when 28K modems were typical and 100KB pages were considered extravagant.
Over the past decade, Craig has written 1,200 tutorials for SitePoint as web standards evolved. Despite living in a technically wondrous future, he has never forgotten what could be achieved with modest resources.
Content
- Jump Start Web Performance
- Notice of Rights
- Notice of Liability
- Trademark Notice
- About SitePoint
- About SiteGround
- About Craig Buckler
- Preface
- Who Should Read This Book?
- Conventions Used
- Code Samples
- Tips, Notes, and Warnings
- Supplementary Materials
- Chapter 1: Web Performance Matters
- The Cost of Poor Performance
- User Costs
- Business Costs
- Environmental Costs
- The Reason for the Woeful Web
- Excuse #1: "We Don't Have a Performance Problem!"
- Excuse #2: "Our Users Never Complain?"
- Excuse #3: "Our Users Have High-end Devices"
- Excuse #4: "Our Customers Use Modern Browsers"
- Excuse #5: "We'll Address Performance Later"
- Excuse #6: "Some Systems Require More Bandwidth and Processing"
- Excuse #7: "Expanding Page Weight is the Price of Progress"
- Excuse #8: "Slimming Pages Means Dumbing Down, with Fewer Features and Effects"
- Excuse #9: "Improving Performance Increases Complications and Maintenance"
- Excuse #10: "Our Client is Happy!"
- Where do I Start?
- Chapter 2: Testing Tools
- Create a Test Plan
- Identify Performance Bottlenecks
- Performance Tool Concepts
- The Browser Rendering Process
- Google Lighthouse/Chrome Audits
- DevTools' Network Panel
- Chrome's Performance Monitor
- Developer Tools' Performance Panel
- DevTools' Console Logs
- performance.now()
- Performance Marks and Measures
- WebPageTest.org
- WebPageTest API
- More Performance Assessment Tools
- Chapter 3: Quick Snacks
- Consider Your Hosting Plan
- Shared Hosting
- Dedicated Server Hosting
- Virtual Private Server (VPS) Hosting
- Cloud Hosting
- Switch to a More Appropriate Hosting Option
- Scale Resources
- Switch Hosts
- Use a Content Delivery Network
- Use Image and Video CDNs
- Asset Management
- Optimal Formatting and Compression
- Art Direction, Sizing, and Effects
- Activate Server Compression
- Activate HTTP/2
- Leverage Browser Caching
- Enable CMS Page Caching
- Are Videos Necessary?
- Check Your Primary Images
- Resize Large Bitmaps
- Choose an Appropriate Image Format
- Avoid Base64 Encoding
- Compress Images Effectively
- Concatenate and Minify CSS
- Concatenate and Minify JavaScript
- Minify HTML
- Load JavaScript at the End of the Page
- Preload Assets
- Remove Unused Assets
- Assess Analytics Performance
- Something More Substantial?
- Chapter 4: Simple Recipes
- Optimize Your Database
- Use a Query Analyzer
- Create Indexes
- Simplify Queries
- Create Additional Database Connections
- Consider a Server or Memory Upgrade
- Cache Results
- Use Background Processing
- Use Alternative Data Systems
- Remove or Optimize Social Media Buttons
- Use URL-based Share Links
- Use the Web Share API
- Be Wary of Third-party Scripts
- Use Responsive Images
- Define Responsive Image Aspect Ratios
- Implement Art Direction
- Lazy Load Images and Iframes
- Play Audio and Video on Demand
- Replace Images with CSS3 Effects
- Use SVGs Effectively
- 1. Add SVGs Using an &img& Tag
- 2. Add SVGs as CSS Background Images
- 3. Embed SVGs into the Page
- Consider Image Sprites
- Consider OS Fonts
- Embed Web Fonts with &link&
- Limit Font Styles and Text
- Use a Good Font-loading Strategy
- Consider Variable Fonts
- Use Modern CSS3 Layouts
- Remove Unused CSS
- Be Wary of Expensive CSS Properties
- Embrace CSS3 Animations
- Avoid Animating Expensive Properties
- Indicate Which Elements Will Animate
- Use CSS Containment
- Check the Save-Data Header
- Adopt Progressive Web App Technologies
- 1. Enable HTTPS
- 2. Create a Web App Manifest
- 3. Create a Service Worker
- Power Down Inactive Tabs
- Consider Inlining Critical CSS
- Provide Accelerated Mobile Pages (AMP)
- Feeling Full Yet?
- Chapter 5: Life-Changing Diets
- Evaluate CMS Templates and Plugins
- Reduce Client-side Code
- Optimize JavaScript Code
- Use JavaScript Sparingly
- Avoid Long-running Tasks
- Bind Events Sparingly
- Analyze Modified Code
- Modify the DOM Effectively
- Cache Regularly Used Nodes
- Minimize Reflows
- Batch-update Styles
- Batch-update Elements
- Use requestAnimationFrame
- Consider Progressive Rendering
- Use Server-side Rendering
- Do You Need a JavaScript or CSS Framework?
- Use a Static Site Generator
- Use a Build System
- Use Progressive Enhancement
- Adopt a Performance Budget
- Create a Style Guide
- Simplify and Streamline
- Learn to Love the Web
- Chapter 6: Check, Please!
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.