"Jamstack is slowwwww." You rarely hear that, especially given Jamstack's reputation for speed. However, even Jamstack sites can suffer performance issues. Don't assume Jamstack automatically equals blazing-fast performance; smart choices are crucial. Let's explore how poor decisions can cripple a Jamstack site's speed.
We'll intentionally build a slow Gatsby site to understand performance bottlenecks. Using continuous performance testing and Google Lighthouse, we'll track every change, starting with a perfect Lighthouse score of 100 and deliberately degrading it to a dismal 17.
Building Our Slow Jamstack Site
We'll use Gatsby. First, install the Gatsby CLI:
npm install -g gatsby-cli
Create a new Gatsby site:
gatsby new slow-jamstack
Navigate to the project directory and start the development server:
cd slow-jamstack gatsby develop
For Lighthouse testing, we need a production build. Vercel provides a convenient hosting solution. Install and log in to the Vercel CLI:
npm install -g vercel-cli vercel
This deploys the site to Vercel. A default Gatsby site is typically fast, scoring 100 on Lighthouse. Let's see how we can sabotage that.
Slowing Down with CSS
CSS frameworks are powerful, but choosing the wrong one or using it inefficiently can hurt performance. Opt for modular frameworks or CSS-in-JS to load only necessary styles.
We'll make a poor choice: loading the entire SemanticUI framework, including jQuery (a dependency), directly into the of our HTML. This requires copying the default
html.js
file:
cp .cache/default-html.js src/html.js
Then, add the SemanticUI stylesheet and jQuery to src/html.js
:
<link href="https://cdn.jsdelivr.net/npm/%5Bemail%C2%A0protected%5D/dist/semantic.css" rel="stylesheet">
Deploy the changes:
vercel --prod
The Lighthouse score drops to 66, a significant decrease simply from loading unnecessary CSS. Time to Interactive (TTI) increases dramatically.
Slowing Down with Marketing Dependencies
Let's add Google Analytics and Facebook tracking scripts to src/html.js
within the :
<!-- Google Analytics --> <!-- Facebook Pixel --> <img src="/static/imghw/default1.png" data-src="https://img.php.cn/" class="lazy" style="max-width:90%" style="max-width:90%" alt="Make Jamstack Slow? Challenge Accepted." >
Deploy again:
vercel --prod
The score plummets to 51. These seemingly small scripts have a substantial performance impact.
Slowing Down with Images
We'll add 100 images from https://placeimg.com
to index.js
, loading them directly without optimization:
const IndexPage = () => { const items = Array.from({ length: 100 }, (_, i) => ( <img key="{i}" src="%7B%60https://placeimg.com/200/200/%24%7Bi%7D%60%7D" alt="{`Image"> )); return ( <layout> {items} </layout> ); };
Deploying again results in a drastically slow site, with a Lighthouse score of 17 and a TTI of 16.5 seconds.
The point? Every decision affects performance. Even on Jamstack, performance isn't free.
Restoring Speed
Jamstack's primary performance advantage is edge caching of static files, reducing Time to First Byte (TTFB). This is faster than server-side rendering. However, client-side optimizations remain essential. While high Lighthouse scores are desirable, remember that they don't always perfectly reflect user experience. This exercise demonstrates that even with Jamstack, diligent attention to performance is required.
The above is the detailed content of Make Jamstack Slow? Challenge Accepted.. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to selectively include CSS on a specific page: 1. Inline CSS, suitable for pages that are not frequently accessed or require unique styles; 2. Load external CSS files using JavaScript conditions, suitable for situations where flexibility is required; 3. Containment on the server side, suitable for scenarios using server-side languages. This approach can optimize website performance and maintainability, but requires balance of modularity and performance.

Flexboxisidealforone-dimensionallayouts,whileGridsuitstwo-dimensional,complexlayouts.UseFlexboxforaligningitemsinasingleaxisandGridforprecisecontroloverrowsandcolumnsinintricatedesigns.

The HTML popover attribute transforms elements into top-layer elements that can be opened and closed with a button or JavaScript. Popovers can be dismissed a number of ways, but there is no option to auto-close them. Preethi has a technique you can u

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

In the following tutorial, I will show you how to create Lottie animations in Figma. We'll use two colorful designs to exmplify how you can animate in Figma, and then I'll show you how to go from Figma to Lottie animations. All you need is a free Fig

We put it to the test and it turns out Sass can replace JavaScript, at least when it comes to low-level logic and puzzle behavior. With nothing but maps, mixins, functions, and a whole lot of math, we managed to bring our Tangram puzzle to life, no J

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.
