Everyone has encountered a splash page in their life online, they're everywhere and they are a silent evil. Often times a company having a web page designed will insist on having a splash page without even realising what such a thing might do to their web traffic and just how bad splash pages are perceived in the community.
The biggest problem with splash pages is that when a search engine's crawler encounters it all they see is a website with practically no content whatsoever so they are less likely to give it a good rank in search results. Recently I even encountered a problem when we had to manufacture content to put on the splash page because the website did not even appear in search results, let alone have a rank.
Another big issue with splash pages is that they usually denote a useless site. When a website is community driven and actually has some proper and interesting content to show there usually is no splash page, just the content. Vice versa seems to go for useless websites where a company might need a splash page simply so that anyone even views their logo and such because they would not spend enough time on the crap website otherwise.
Also there is the law of three clicks, where it is advised that any content is accessible via only three clicks, a splash page adds at least one of those. Personally when I see a splash and am not particularly interested already I just leave.
Continue reading about Splash pages
Semantically similar articles hand-picked by GPT-4
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️