Images can also be loaded via absolute URLs from CDNs:
Query Parameters & URL Encoding
This link sends search parameters to a search page. Note the URL-encoded space (%20):
Search HTML Tutorials
Contact Section
You successfully jumped to this section using a fragment identifier URL!
```
---
## Best Practices & Common Pitfalls
### 1. Always Use Lowercase URLs
Web servers running on Linux/Unix (which make up the vast majority of the web) are case-sensitive. While `example.com/About.html` and `example.com/about.html` might work on a Windows-based local development server, the link will break when deployed to a Linux server if the casing does not match exactly. Keeping all URLs strictly lowercase prevents these issues and improves SEO.
### 2. Prefer Protocol-Relative or HTTPS URLs
Avoid hardcoding `http://` for external assets. If your site runs on `https://` and you attempt to load an image or script via `http://`, the browser will block it as "Mixed Content." Always use `https://` or protocol-relative URLs (e.g., `//cdn.example.com/script.js`), which automatically match the protocol of the hosting page.
### 3. Use Root-Relative URLs for Main Navigation
When building multi-level websites (e.g., pages inside folders like `/blog/news/post.html`), document-relative links like `about.html` or `../about.html` can easily break if a page is moved. Use root-relative URLs starting with a forward slash (e.g., `/about.html`) for your header and footer navigation to ensure they work seamlessly across the entire site.