Why is there a need for another framework? the current approach is not producing fast sites, and this problem will not disappear by waiting for a faster CPU.

Foreword

Qwik in Action

Introduction to the frontend development. Now, the responsibility of creating good or bad applications depends on you because the means available are all there.

Introduction

Overview of TypeScript. TypeScript introduced types into an untyped language like Javascript to ensure code consistency.

TypeScript

Overview of the frontend architectures. In this lesson you will understand the difference from Client Side Rendering and Multi Page Application.

Frontend architectures

Overview of the hydration. In this lesson you will understand the difference from Hydration and Island architecture/Partial Hydration.

Hydration

React Server Component. In this lesson you will understand the difference from Server Component and Client Component.

React Server Component

Qwik resumability will change the frontend ecosystem, In this lesson you will understand why is so great.

Resumability, the Qwik way

Wrap up of frontend architectures module.

Summary Chapter 2

In this lesson you will be able to understand more about performance and you will understand how improve your application with less JavaScript.

Qwik, the framework built on top of closure-extraction

Resumability is the core concept behind Qwik. In this lesson you will understand better the process.

Resumability

Code Extraction is a topic hard to master, you will understand how it works with different approaches.

Code Extraction

JSX syntax is the most famous one because of React, but what about the other frameworks, Vue, Angular?

Why Qwik use JSX syntax

Summary Chapter 3

Let's see together the fundamentals of Qwik. In this lesson you will compare Webpack and Vite.

Getting started with Qwik

The Qwik build process is so important because the resumability process requires correct and intelligent bundling.

Qwik compilation Process

Qwik CLI and amazing tool to have a great Developer Experience with Qwik.

Technical requirements to start a new Qwik application

Qwik Middleware an easy and clever way to expose your RESTful APIs or GraphQL APIs.

Middleware

Wrap up of Getting Started with Qwik module.

Summary Chapter 4

In this lesson you will learn the pillars of SEO. You will lean few new terms and metrics that can help you to measure your application.

In this lesson you will learn the some new things about SEO and crawler.

Sitemap and robots files

Partytown an amazing library to execute third scripts in the service worker.

Partytown

Core Web Vitals are so important for own application. You will learn in detail all the metrics.

Core Web Vitals

Core Web Vitals Labs Data vs Field Data. These two information are so different, let's figure out the peculiarity of those.

Labs data vs Field data

Summary Chapter 5

SEO and Core Web Vitals

There are many ways to deploy a Qwik application. You can have your own server and deploy your Qwik application easily with the Qwik CLI and integrations.

Deploy Qwik in production

Cloud solution are a good alternative for a low cost pipeline and host. Nowadays these kind of services are so smart and great, you should try them.

Cloud solutions

With different team and many developers, it's important to master branching strategies to avoid problems during your day by day.

Branching strategies

Progressive Web App approach can be an alternative to the stores. You can publish you application with a lot of benefit with PWA.

Progressive Web App

Wrap up of Deploy Qwik in Production module.

Summary Chapter 6

Style an application is so important let's see how engage your Stakeholders into this process.

Style and render data with Qwik

CSS is so huge, there are a lot of ways to style your application with Qwik, let's see them together.

CSS and Built-In Styling Methods

Tailwind is an amazing library, let's see together how master it. I will share you some tips and tricks to use Tailwind in a better way.

Tailwind CSS

In this lesson you will learn how manage data with Qwik. There are a lot of APIs to explore, let's jump into the code.

Managing data with Qwik

Summary Chapter 7

In this lesson you will learn how architect a modern frontend end application.

Creating an e-commerce with Qwik and Supabase

In this lesson you will learn the trade offs of technical decisions. I share with you some tips and tricks.

Technological spike

In this lesson you will explore Supabase. This is an amazing service to leverage your business.

Supabase for your backend

A custom authentication is too complex and risky to implement from scratch. Let's use the Supabase auth to optimize our goals.

Let's talk about the Authentication process

Summary Chapter 8

Supabase CLI an handy tool to improve consistency across environments.

Supabase CLI

Let's use the Supabase CLI to manage our database migrations and schemas.

Supabase db migrations

In this lesson you will create the e-commerce homepage with the Supabase client to read the data.

Show products on our homepage

Every e-commerce has a detail page, let's create our product detail page with Qwik.

Product Detail

Cache is really useful and in this lesson I will explain in the detail how it works. I will share my experience in this topic with some cool analogies.

Cache-control headers

Summary Chapter 9

Rendering products with Orama full text search

Let's improve out application with a useful "Add to favorites" feature.

Add a product to your favorites list

In this lesson you will learn how to use Stripe to manage your payments in a secure way.

Adding cart and checkout process with Stripe

Let's try the Supabase database function. This is an easy way to allows us to do several things and also add some logic to our procedure.

Page views tracking

A real-time database with Supabase is so simple to implement, let's build together a new functionality with this great feature.

Real-time database

Summary Chapter 10

Let's explore together the benefit of testing. In this lesson you will explore the various types of tests, Unit Test, E2E, Visual regression tests and more.

Overview of application testing

Let's discuss together how and when testing is valuable for our business. 3X Explore/Expand/Extract can help us is this reasoning.

How much testing is enough? When do I write tests?

In this lesson you will lean the Test driven development TDD flow. It's a really good practice to put in place.

Test-Driven Development (TDD)

In this lesson you will lean how test your components with Cypress.

Let's add some tests with Cypress

Do you need a Qwik component library? Qwik UI is the project for you because can give you a lot of Qwik accessible components out of the box.

Qwik UI

Summary Chapter 11

Adding tests to our Qwik application

Let's explore a bit of history of Qwik. A new framework with a great past.

Final thoughts

Qwik and React together, no problem, qwikify$ is the API to solve your problems.

qwikify$

Qwik and Astro together, no problem, @qwikdev/astro is the library to solve your problems.

Qwik inside Astro application

Qwik and micro-frontends together, no problem, out of the box Qwik can manage this scenario with no external dependencies.

Micro-frontends with Qwik

Summary chapter 12

Enter your name and email address below, then click the **"Send my free chapter"** button to get started

250+ page PDF

EPub

newline Access with Replits

All Code Samples

Discord Community Access

One-time price of $69

( the primaryDescriptionMarkdown is long - several lines, include images, as long as you want )

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

In <the length of these lessons> we cover <three salient points about what we cover. Your BEST points>. Its <however long it is> and comes with <these bonus features, and reasons to buy. code, etc.>

It's taught by <author name> who <credibility, reason you should listen to them>. <social proof, if you have it yet>

<then you can list other supporting stuff you want to add, anything you want here>

-------
Example:
-------

We created a free course to create your first GraphQL server (from scratch) using Node and TypeScript. TypeScript and GraphQL are a powerful combo, but there's a lot of confusing edges if you're getting it setup the first time.

In this course we cover the basics of getting TypeScript setup with Node, how GraphQL works, and how to set up a GraphQL server using Apollo server. It's two hours long, it comes with complete code examples, and we walk through the code step-by-step.

It's taught by my friend, Shopify-engineer Hassan Djirdeh and he's integrated what he's learned using GraphQL in production as an engineer at Shopify. We've already had over 1,300 students enroll and it's been getting great reviews so far.

// ... and so on

Harness Qwik Resumable Architecture for Lightning-Fast Startup Times

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

( the summary is short - one or two lines )

Complete Guide to Qwik

SEO stands for Search Engine Optimization and is a set of best practices to ensure that a site is well-indexed by search engines. This optimization will bring advantages in terms of traffic, and therefore, the business will also benefit significantly. This chapter will explore some best practices to ensure the application is perfectly configured for excellent SEO.

It's important to understand that search engines scan web pages to index websites and ensure that the result of a search is as accurate as possible. This scan has a limited time for each site, and therefore, the more useful information that can be provided in this short time, the better it is for the site/application. The architectures seen in the previous chapters, Server Side Generation and Server Side Rendering, can be used to provide a quality result in the shortest possible time. These two approaches guarantee the return of an HTML page containing crawlable content to the search engine crawler. So, if these technologies are used, a good start is ensured.

The fundamental aspect of obtaining a good ranking is to have interesting content or provide a useful and frequently used service. The more visitors a site receives, the more the search engine will consider it an interesting result to show. It is not only necessary that the content attracts users, but visitors must also spend time within the application.

A first metric to consider and constantly monitor is the 

 because it indicates how much people appreciate or, more importantly, don't appreciate the application or the user experience.
This metric measures how many people visit a single page on the application or site and don't interact with the page before leaving.
According to Google, 

’s engaged sessions meet at least one of the following conditions:

So, for example, it measures users who leave an e-commerce site without purchasing something or interacting (e.g., clicking a link).
The contents can certainly influence this metric, but it could also depend on the application's loading time, which is too slow, and therefore, the user prefers to choose one of the competitors. Fortunately, with the use of Qwik, any slowness problems can be avoided.

 value means that the user's overall session duration is short. On the other hand, a low value means that they spend time on the page and interact with it.
It should be noted that a high value cannot always be considered negative; it all depends on what type of application is in use. For example, if the application provides news or other content that involves sessions from a single page, it is perfectly normal to have a high bounce rate value. If this is not the case, then this high value is a bad thing.
A bounce rate of 35% or less is good, while a bounce rate of 60% or more is high, and therefore, there is room for improvement and encouragement for users to stay more in the application.

By measuring the time that users spend on a page before returning to the Search Engine Results Pages (SERP) we can obtain what is defined as "Dwell time".
How long does the user stay on a page before moving away? This metric answers exactly this question.
Let's say you are looking for how to integrate Google Maps with Qwik, and from the search results, you click on one of the first results. It's a page full of advertisements, so you go back to the SERP after only 5 seconds; the Dwell time is, therefore, 5 seconds.
You click on another article, and it is well-written, pleasant to read, and very useful. You spend several minutes reading the detailed description; in this case, the Dwell time is much higher.

On the other hand, users may find the information they need at the top of the page and quickly return to the SERP, so a shorter dwell time does not necessarily indicate lower content quality or user dissatisfaction.
The algorithms that calculate the ranking are not public; therefore, the best practices are the result of the experience that various experts have shared. Given the statement made earlier, Dwell time is probably not a ranking factor, at least not a direct one.
However, dwell time can still provide insights into user behavior. If users tend to stay on the pages longer, it could mean they find the content engaging, and shorter stays could mean there are underlying issues causing users to bounce off the pages.

---
title: SEO
description: In this lesson you will learn the pillars of SEO. You will lean few new terms and metrics that can help you to measure your application.
---

# SEO

SEO stands for Search Engine Optimization and is a set of best practices to ensure that a site is well-indexed by search engines. This optimization will bring advantages in terms of traffic, and therefore, the business will also benefit significantly. This chapter will explore some best practices to ensure the application is perfectly configured for excellent SEO.

It's important to understand that search engines scan web pages to index websites and ensure that the result of a search is as accurate as possible. This scan has a limited time for each site, and therefore, the more useful information that can be provided in this short time, the better it is for the site/application. The architectures seen in the previous chapters, Server Side Generation and Server Side Rendering, can be used to provide a quality result in the shortest possible time. These two approaches guarantee the return of an HTML page containing crawlable content to the search engine crawler. So, if these technologies are used, a good start is ensured.

The fundamental aspect of obtaining a good ranking is to have interesting content or provide a useful and frequently used service. The more visitors a site receives, the more the search engine will consider it an interesting result to show. It is not only necessary that the content attracts users, but visitors must also spend time within the application.

## Bounce rate

A first metric to consider and constantly monitor is the `bounce rate` because it indicates how much people appreciate or, more importantly, don't appreciate the application or the user experience.
This metric measures how many people visit a single page on the application or site and don't interact with the page before leaving.
According to Google, [GA4](https://support.google.com/analytics/answer/10089681)’s engaged sessions meet at least one of the following conditions:

-   Lasts longer than 10 seconds
-   Has a conversion event
-   Has 2+ page views

So, for example, it measures users who leave an e-commerce site without purchasing something or interacting (e.g., clicking a link).
The contents can certainly influence this metric, but it could also depend on the application's loading time, which is too slow, and therefore, the user prefers to choose one of the competitors. Fortunately, with the use of Qwik, any slowness problems can be avoided.

A high `bounce rate` value means that the user's overall session duration is short. On the other hand, a low value means that they spend time on the page and interact with it.
It should be noted that a high value cannot always be considered negative; it all depends on what type of application is in use. For example, if the application provides news or other content that involves sessions from a single page, it is perfectly normal to have a high bounce rate value. If this is not the case, then this high value is a bad thing.
A bounce rate of 35% or less is good, while a bounce rate of 60% or more is high, and therefore, there is room for improvement and encouragement for users to stay more in the application.

To calculate this value, [Google Analytics](https://support.google.com/analytics/answer/10089681) can be used.

## Dwell time

By measuring the time that users spend on a page before returning to the Search Engine Results Pages (SERP) we can obtain what is defined as "Dwell time".
How long does the user stay on a page before moving away? This metric answers exactly this question.
Let's say you are looking for how to integrate Google Maps with Qwik, and from the search results, you click on one of the first results. It's a page full of advertisements, so you go back to the SERP after only 5 seconds; the Dwell time is, therefore, 5 seconds.
You click on another article, and it is well-written, pleasant to read, and very useful. You spend several minutes reading the detailed description; in this case, the Dwell time is much higher.

On the other hand, users may find the information they need at the top of the page and quickly return to the SERP, so a shorter dwell time does not necessarily indicate lower content quality or user dissatisfaction.
The algorithms that calculate the ranking are not public; therefore, the best practices are the result of the experience that various experts have shared. Given the statement made earlier, Dwell time is probably not a ranking factor, at least not a direct one.
However, dwell time can still provide insights into user behavior. If users tend to stay on the pages longer, it could mean they find the content engaging, and shorter stays could mean there are underlying issues causing users to bounce off the pages.

## Semantic HTML

It is known for sure that if websites are difficult to read, they are ignored by search engines because they prefer those that have been updated with modern HTML features. Therefore, sites built a long time ago are disadvantaged.
One of the characteristics of modern websites is the use of HTML5, which has very specific semantics that search engine crawlers prefer because it is more understandable by better defining the different sections and layout of the web pages.