Your portfolio loads in 4 seconds. In that time, 25% of mobile visitors have already left. The ones who stayed are now forming an opinion — and "slow website" is not the impression you want to give.
Page speed matters more than most people realise. Here's what's behind it, and why the way your portfolio is built determines how fast it loads.
The Speed Problem With Page Builders
Most people build websites using platforms like WordPress, Wix, Squarespace, or Webflow. These are powerful tools. They're also slow by default.
When you visit a WordPress website, the browser doesn't just download your content. It downloads:
- The WordPress core framework
- The theme files (often 500KB–2MB of CSS and JavaScript)
- Every plugin that's installed (SEO plugin, contact form plugin, analytics plugin, slider plugin...)
- External fonts, external scripts, external trackers
What a Hand-Coded Portfolio Does Differently
A hand-coded portfolio — like every site built by Footprint Forge — doesn't have this problem.
The HTML file is small. The CSS is minimal and specific to that site. There's no framework overhead, no plugin bloat, no unnecessary scripts. The browser makes 5–10 file requests. On any connection, that's under a second.
The difference isn't theoretical. Run any WordPress portfolio and any hand-coded portfolio through Google PageSpeed Insights and compare the scores. The gap is typically 40–60 points.
Why Speed Matters for SEO
Google has explicitly used page speed as a ranking factor since 2010. In 2021, they introduced Core Web Vitals — a set of specific speed metrics that now directly affect search rankings.
The three Core Web Vitals that matter most:
Largest Contentful Paint (LCP): How long until the main content appears. Google wants this under 2.5 seconds. Most WordPress sites fail this on mobile.
First Input Delay (FID): How long until the page responds to a click. Google wants under 100ms. Heavy JavaScript frameworks fail this frequently.
Cumulative Layout Shift (CLS): Whether elements shift around while loading. A common problem with image-heavy template sites.
A hand-coded portfolio, built cleanly and hosted on a fast CDN like GitHub Pages, passes all three easily. A WordPress portfolio with default settings fails all three.
Why Speed Matters for Credibility
Beyond SEO, there's a simpler reason speed matters: it's a proxy for quality.
When someone scans your QR card and your portfolio loads instantly, they form an impression: professional, well-made, reliable. When it loads slowly — or worse, fails to load on a slow connection — the impression is the opposite.
For a banking professional, consultant, or founder, "my website is slow" is not a benign fact. It's a credibility signal. If you can't be bothered to have a fast website, what else are you not bothered about?
GitHub Pages: The Speed Advantage
Every Footprint Forge portfolio is hosted on GitHub Pages, served through a global CDN (Content Delivery Network).
A CDN stores copies of your website files in data centres around the world. When someone visits your site from Chennai, they get the files from the nearest server — not from a shared hosting server in Mumbai that's handling 500 other websites simultaneously.
The result is consistent, fast loading anywhere in India. Even on 4G mobile connections, the portfolio loads in under a second.
Images: The Most Common Speed Problem
The single most common cause of slow portfolio websites is unoptimised images.
A DSLR photo is typically 4–8MB. If you upload that directly to your portfolio, every visitor's browser has to download a 4–8MB file before the page looks complete. On a 4G connection, that's 2–4 seconds just for one image.
At Footprint Forge, all images are compressed and resized before being added to portfolios. A profile photo that started at 5MB typically becomes 80–120KB after optimisation — with no visible quality difference on a phone screen.
The Practical Takeaway
When evaluating how your portfolio is built, ask one question: how many unnecessary things does the browser have to download before my content appears?
For a hand-coded portfolio on GitHub Pages: very few. For a WordPress portfolio on shared hosting: many.
Speed isn't just a technical detail. It's a user experience decision, an SEO decision, and a credibility decision. Get it right from the start.