Why is it SO DANG HARD in ecommerce to get a fast mobile PageSpeed, and am I wasting my time trying to achieve a better time?

If there’s one thing that makes me feel like an enormous loser, it’s running Google PageSpeed scores on my website.For mobile, depending on how the test is feeling at a particular time, I’ll get scores between 10 and 25 on mobile—and between 60-85 on desktop. Seeing myself so deep in the red makes me feel like a GIGANTIC fucking loser, and it makes me desperate to try to get rid of a bunch of shit on the site to achieve a faster score.It eats at me to the point where I consider eliminating functions on the site that add genuine, real value, just to get a PageSpeed boost. I’ve considered doing such hugely moronic things as: Getting rid of a reviews app (despite reviews being so critical in ecommerce); further compressing my already highly-compressed images to the point that they would be blurry and look like shit (on a site that sells wall art, no less); deactivating the “Buy Now” button that allows them to go straight to checkout; etc. Trying to improve the speed scores turns me into a huge dumbass basically, considering doing stupid stuff just to see that red turn orange.The thing is, when I test competitor sites in my same industry — huge, behemoth companies that get tons of traffic and have huge budgets to improve their site speed — their scores are shit too! Sites like iCanvas, GreatBigCanvas, even Amazon itself — all of their mobile PageSpeeds are in the red too! Somewhere in the ballbark of between 20-30. All of them also FAIL the Google CoreVitals test on mobile.So when I see that, from such huge successful companies that have titanic budgets to spend on these things, it makes me think: Maybe I’m wasting my time and overthinking this? Maybe it’s easy to get faster scores if you’re just doing something basic like hosting blog articles, or having a landing page that describes attorney services and tries to get leads to book a call — but a highly interactive product page for commercial sales of visual products like wall art? Maybe there’s only so far you can push this–and chasing high mobile PageSpeed scores for such a site is like chasing a leprechaun at the end of the rainbow?Your thoughts on this? Specifically, how do you strike that tradeoff between: Having features & functions on your site that genuinely add value (yet increase page weight and cause load times to be delayed), vs. eliminating a bunch of stuff to boost load times (while simultaneously getting rid of features that add value)I see all the stats on how “X extra milliseconds in load time causes a Y percent drop in conversions”, and I get that — but then I see all these companies who are just flooded with customers *also* have shit load times, so maybe it’s not where I should focus my energies on?This is something I truly struggle with, and I’ll go through phases where I’m wearing my “increase page speed” hat and I’ll maybe push it too far in one direction, then I’ll go through another “add more functionality on the site” phase to where I’ll do stuff that will decrease the load times.Any insight into how you think about this and balance these different factors would be much appreciated, because this really is something that frustrates me and makes me feel like a huge loser.Example product page of my site is — > https://nextlevelartwork.com/products/velociraptor-funny-classy-dinosaur-portrait-poster-or-canvas-artOne thing I will note, despite whatever the almighty Google test tells me: My site doesn’t feel slow when I use it, whether on mobile or desktop. Even after I completely clear my cache. To me, it feels reasonably smooth and fast. Maybe that first load, initial, cache-less load on mobile will take a little bit, product pages do take a few seconds to fully load everything to the point where scrolling & interactivity is 100% smoothly responsive, but it’s not agonizing, and after that point, the rest of the site session feels pretty smooth. So maybe I’m overthinking this and putting too much stock into Google telling me I suck, vs what the actual felt user experience is.Thanks!

Proprietary vs. Open-Source: How to Choose the Right CMS

There are a ton of content management system (CMS) options out there. And if you’re looking to find the perfect fit your website project, the search can be exhausting. Particularly if you don’t have a lot of experience with these systems. But before you even choose a specific app, there’s another factor that needs to…

17 Best Video Background Plugins for WordPress

Having trouble getting your website’s message across? Need an interactive and eye-catching way to draw in more traffic? CodeCanyon and Envato Elements has many high-quality video background plugins available for you to add to your WordPress website and to help amplify your site’s message and engage visitors. These video background plugins are rich with features…

Using New Gatsby Source WordPress Plugin

In my previous article, I discussed how I learned to create a decoupled WordPress powered Gatsby site using the Gatsby Source WPGraphQL plugin. The project was done following the ongoing developmental version of WPGraphQL and an excellent tutorial by Henrik Wirth. Although WPGraphQL was used in some production sites at that time, there were lot…

A Complete Guide To Incremental Static Regeneration (ISR) With Next.js

A year ago, Next.js 9.3 released support for Static Site Generation (SSG) making it the first hybrid framework. I’d been a happy Next.js user for about a few years at this point, but this release made Next.js my new default solution. After working with Next.js extensively, I joined Vercel to help companies like Tripadvisor and…

Best PHP Invoicing and Billing Scripts

Do you want to automate your billing and invoicing process and receive payment faster? PHP invoicing scripts will streamline your billing and invoicing process and make it more efficient.  These scripts come with customizable templates that help you build professional invoices. They can also automatically attach and send PDF invoices to your customers via email…

I just got really overwhelmed…

I’m currently doing a tutorial on Web Development and I hit the part of the course where we are now making our site live. The instructor used Bluehost and said we can use any host we wont. So I thought I would do some research on Bluehost and see if they are any good.I’ve read mixed reviews so far and someone recommended Digitial Ocean and Siteground. Both seemed very nice and reasonably priced. I know this is just a tutorial but I want to pick a good hosting site for the future of my projects.This is where I am getting overwhelmed…I have also been told about AWS and GitHub being a good host. So I went to check out AWS and got super overwehlmed. I had no idea what I was looking at. They offer so many different services, which one do I choose? This is the page where I was starting to stress out lol. Is AWS a good place to host your sites?I’m not looking to be a full-time freelancer but I would eventually like to take on projects and build sites for companies, front-end, and back-end. Pictures, buttons, videos, etc, all on the site. Is that what AWS is for?And yes, I will be doing my own research/learning about AWS but for now I would just like a simple explanation of the service: GitHub vs AWSEDIT: Namecheap also offers hosting services, any thoughts on going with them?

We built a deployment SaaS from scratch, and recently got our first paying user (lessons learned + stats + UX evolution)

Hi Reddit!I’m Wouter Besems, co-founder of Launchdeck. I’d like to share with you our story and some of our key take-aways – outlining how me and my co-founder have spent time building our product and ultimately introducing a pricing model – and acquiring our first paying (“premium”) customer shortly after that.We’d love to get your feedback both on the product and our current strategy.tl;dr:https://launchdeck.ioLaunchdeck is an automated deployment service which lets you easily publish sites and applications from a Git repository to a server.Tech stackNode.js (express) back-endTypeScript (React.js) front-endLocal development environment runs directly on our machines “bare metal” – super fast integration and debugging workflow.Our staging- and production clusters are powered by a cloud provider and are based on a set of docker images with MongoDB and Redis providing our data layer.Stats7360 hours logged between the two foundersApproximately 35k lines of code23 internal repositories, of which 8 open source2100 signupsFirst paying customer on February 4, 2021Our storyLaunchdeck is founded, built by, and run by two people. My day job consists of front-end development and online marketing, and my co-founder is a full-stack developer. Even though we feel this is theoretically the perfect team for building and launching a SaaS product, a trajectory that was supposed to take one year ended up taking four (neither of us could work on the product full-time – my co-founder got his degree 2 years into the project and we are both still holding part-time positions, however we tried to take all this into account in our initial estimations).Where it beganLet’s backtrack a little bit. When I met my co-founder, we were both employed at a web agency and we ran into an issue where deploying code to a server wasn’t exactly straightforward.To deploy a small project, manually uploading using FTP seemed like the most obvious way. A huge hurdle was, however, keeping track of modified files that needed to be uploaded, and whenever something went awry, it was tricky to roll back to a previous version. On top of that, with all the build tooling entering the landscape, we would be forced to run a local build for every small adjustment made.At that point, existing deployment solutions were either overly complicated (especially for smaller projects) or were very expensive. We were looking for something well-suited for PHP-based and static applications (with or without a frontend bundle), and something that freelancers and small-to-medium size teams could understand without the need for a dedicated in-house DevOps – and we’ve mostly kept our focus there.Scratching our own itchIt wasn’t long before we had figured out our own solution: a CLI-based open source build automation toolkit that essentially just clones a repository, optionally runs some build commands, and uploads the resulting files to a server. Still, to this day, this core part of our build automation service remains open source: https://github.com/launchdeckioBecause a CLI tool can be somewhat limiting in user friendliness and visual appeal, we quickly realised we wanted to add a visual user interface and host the service in the cloud so that it didn’t have to run locally. 4 years and 7,360 hours of design- and programming work later, we’re now at the point of having a SaaS solution that allows web developers to quickly and easily ship their projects without needing to have the prerequisite knowledge of dev-ops or systems administration.Rolling out the pricing modelDuring this time, while we had beta users trying and testing our platform, we continued developing the product and eventually, earlier just this year, we introduced our premium pricing tiers.A lot of time has gone in the UI design, which throughout the years has been finetuned and most importantly: simplified. Screenshots of the various stages of this process have been included at the bottom of this post.Shortly after introducing our paid plans, we acquired our first paying customer: a great milestone! Currently we’re experimenting with various marketing campaigns and are still trying to find the optimal channels of communication. Advice would be really appreciated!Things we’ve learned along the wayPlanning: If there was one place where we were way off, it’s the amount of time it would take to build a solid deployment automation service. During most of the development process, we were both studying and/or working part-time on other projects, which meant time wasn’t always as abundant as we would have liked.Assumptions regarding functionality: over the years, we’ve made numerous assumptions regarding what we thought would make our service better. This caused us to, in at least a number of cases, focus on features that weren’t all that important to our end users. That is, in hindsight of course :)When working on new features, we iterated quickly and only once there was a functional version allowing us to actually test the feature, and we decided we actually wanted to move forward with this feature, we would go back in and clean up (or rewrite partly) the implementation to prevent build-up of ‘tech debt’ as much as possible. We’ve always been rather thorough with this – and it’s still paying off to this day.When picking the right technology we’ve tended to err on the side of safe and battle-tested frameworks, libraries and languages with a wide community backing. This has worked out very favorably in every single case although some luck may be involved there.Not a brand-new insight, of course, but splitting different parts of the codebase into individual modules or services forces you to think about abstractions (helpful) and means additional flexibility when you’d like to use a certain language or framework for a new feature or part of the ecosystem.As a first SaaS product, a deployment automation service isn’t exactly low hanging fruit. A lot had to be built from scratch (there’s no such thing as a “deployment SaaS starter kit”). Besides that, most similar competitors will have at least some 5 to 10 developers on their team. Only after 4 years of development, we’ve arrived at the point of being able to charge a fee for our product.Paid marketing: Costs for this tend to rise quickly when you’re still in the process of determining who exactly is your target audience, and what channel to use for optimal conversion. It seems to us that “conventional” channels such as AdWords, Facebook and LinkedIn are expensive but ineffective, or at least for the type of customer we’re trying to attract. We’re broadening our range now looking at sharing content to various communities such as Indie Hackers, Reddit and Hackernews.Mapping out the futureWe’re currently working to figure out the right marketing channels, and doing so with a limited budget. As our funnel becomes more profitable, we can afford to spend more time on building and expanding Lauchdeck. This is our current roadmap:Config file editor: Which lets users add and edit configuration files (such as wp-config.php or .env) without having to manually log into their server.Fully automated deployments for staging and test environments with an intelligent queue to deal with ongoing operations and starting new builds.More support for a variety of target servers or platforms such as DigitalOcean, AWS or even a proprietary hosting infrastructure so the user no longer has to bother with the server setup part of the configuration.Evolution of UXOur very first mockupFirst UI designUI redesignLaunchdeck UI 2021

How To Get Web Design Clients Fast (Part 2)

In part 1, we explained how to use a monthly recurring revenue (MRR) model to grow your web design business. In this second part, we’ll explain how to use proven sales techniques to keep scaling your business profitably. If you’re an agency owner, you know that you need customers to grow. No matter how big…