A Technical search engine marketing Information to Superior Core Internet Vitals Optimization

Editor’s notice: As 2021 winds down, we’re celebrating with a 12 Days of Christmas Countdown of the most well-liked, useful skilled articles on Search Engine Journal this yr.

This assortment was curated by our editorial group based mostly on every article’s efficiency, utility, high quality, and the worth created for you, our readers.

Every day till December twenty fourth, we’ll repost among the finest columns of the yr, beginning at No. 12 and counting right down to No. 1. Our countdown begins right now with our No. 6 column, which was initially printed on April 26, 2021.

This in-depth technical search engine marketing information on superior Core Internet Vitals by Jamie Indigo was well-received by readers. It’s packed full of knowledge and actionable recommendation on diagnose, measure, and enhance website efficiency by way of human expertise.

Actually nice work on this, Jamie! We recognize all the good content material you proceed to contribute to SEJ.

Get pleasure from!

---

Actual people need good net experiences. What does that appear to be in follow?

Effectively, one current examine cited by Google in a weblog put up about Core Internet Vitals discovered that cell net customers solely saved their consideration on the display screen for 4-8 seconds at a time.

Learn that once more.

You might have lower than 8 seconds to ship interactive content material and get a person to finish a activity.

Enter Core Internet Vitals (CWV). These three metrics are designed to measure website efficiency in human expertise. The open-source Chromium undertaking introduced the metrics in early Might 2020 and so they had been swiftly adopted throughout Google merchandise.

How can we qualify efficiency in user-centric measurements?

1. Is it loading?
2. Can I work together?
3. Is it visually secure?

Essentially, Core Internet Vitals measure how lengthy it takes to finish the script capabilities wanted to color the above-the-fold content material. The sector for these Herculean duties is a 360 x 640 viewport. It matches proper in your pocket!

This war-drum for unaddressed tech debt is a blessing to lots of product house owners and tech search engine marketing professionals who’ve been backlogged in favor of recent options and glossy baubles.

Is the Web page Expertise replace going to be Mobileggedon 4.0?

Most likely not.

However when your web page passes CWV assessments, customers are 24% much less more likely to abandon web page masses. These efforts profit each supply and medium, and most significantly – actual people.

The Web page Expertise Replace

For all the excitement, CWV might be parts in a rating sign. Anticipated to roll out steadily mid-June via August 2021, the Web page Expertise Rating might be comprised of:

1. Core Internet Vitals.
2. Cellular-Pleasant.
3. Secure Shopping.
4. HTTPS.
5. No Intrusive Interstitials.

Up to date documentation clarifies that the rollout might be gradual and that “websites usually shouldn’t count on drastic adjustments.”

Vital issues to know concerning the replace:

• Web page Expertise is evaluated per URL.
• Web page expertise is predicated on a cell browser.
• AMP is not required for High Tales carousels.
• Passing CWV is just not a requirement to seem in High Tales carousels.

A New Web page Expertise Report In Search Console

Search Console now features a Web page Expertise report. The contemporary useful resource consists of backdated information for the final 90 days.

To ensure that a URL to be “Good,” it should meet the next standards:

• The URL has Good standing within the Core Internet Vitals report.
• The URL has no cell usability points in response to the Cellular Usability report.
• The location has no safety points.
• The URL is served over HTTPS.
• The location has no Advert Expertise points, or the location was not evaluated for Advert Expertise.

The brand new report gives high-level widgets linking to experiences for every of the 5 “Good” standards.

Workflow For Diagnosing & Actioning CWV Enhancements

First, an essential caveat relating to Area vs Lab information.

Area Knowledge is efficiency information collected from actual web page masses your customers are experiencing within the wild. You may additionally hear Area Knowledge known as Actual Consumer Monitoring.

Core Internet Vitals assessments and the Web page Expertise Rating Sign will use Area Knowledge gathered by the Chrome Consumer Expertise Report (Crux).

Which Customers Are Half Of The Chrome Consumer Expertise Report?

Crux information is aggregated customers who meet three standards:

1. The person opted-in to syncing their searching historical past.
2. The person has not arrange a Sync passphrase.
3. The person has utilization statistic reporting enabled.

Crux is your supply of reality for Core Internet Vitals Evaluation.

You’ll be able to entry Crux information utilizing Google Search Console, PageSpeed Insights (page-level), Public Google BigQuery undertaking, or as an origin-level dashboard in Google Knowledge Studio.

Why would you utilize anything? Effectively, CWV Area Knowledge is a restricted set of metrics with restricted debugging capabilities and necessities for information availability.

Why Doesn’t My Web page Have Knowledge Accessible From Crux?

When testing your web page, you might even see “The Chrome Consumer Expertise Report doesn’t have ample real-world velocity information for this web page.”

It is because Crux information is anonymized. There should be sufficient web page masses to report with out the cheap chance of the person person being recognized.

Internet Core Vitals are greatest recognized utilizing subject information after which identified/QAed utilizing lab information.

Lab Knowledge permits you to debug efficiency with end-to-end and deep visibility into UX. It’s referred to as “lab” as this emulated information is collected inside a managed atmosphere with predefined machine and community settings.

You will get lab information from PageSpeed Insights, net.dev/measure, Chrome DevTool’s Lighthouse panel, and Chromium-based crawlers like a neighborhood NodeJS Lighthouse or DeepCrawl.

Let’s dive right into a workflow course of.

1. Determine Points With Crux Knowledge Grouped By Habits Patterns In Search Console.

Begin with Search Console’s Core Internet Vitals report back to establish teams of pages that require consideration. This information set makes use of Crux information and does you the kindness of grouping collectively instance URLs based mostly on habits patterns.

For those who clear up the basis concern for one web page, you’re more likely to repair it for all pages sharing that CWV woe. Sometimes, these points are shared by a template, CMS occasion, or on-page ingredient. GSC does the grouping for you.

Deal with Cellular information, as Google is shifting to a Cellular-First Index and CWV is ready to have an effect on cell SERPs. Prioritize your efforts based mostly on the variety of URLs impacted.

Click on into a difficulty to see instance URLs that exhibit the identical habits patterns.

Save these instance URLs for testing all through the advance course of.

2. Use PageSpeed Insights To Marry Area Knowledge With Lab Diagnostics.

When you’ve recognized pages that want work, use PageSpeed Insights (powered by Lighthouse and Chrome UX Report) to diagnose lab and subject points on a web page.

Keep in mind that lab assessments are one-off emulated assessments. One check is just not a supply of reality or a definitive reply. Check a number of instance URLs.

PageSpeed Insights can solely be used to check publicly obtainable and indexable URLs.

For those who’re engaged on noindex or authenticated pages, Crux information is obtainable by way of API or BigQuery. Lab assessments ought to use Lighthouse.

3. Create A Ticket. Do The Improvement Work.

I encourage you as search engine marketing professionals to be a part of the ticket refinement and QA processes.

Improvement groups usually work in sprints. Every dash consists of set tickets. Having well-written tickets permits your improvement group to higher measurement the hassle and get the ticket right into a dash.

In your tickets, embrace:

Consumer Story
Observe a easy format:

As a < sort of person/website/and many others >, I would like < motion > with a purpose to  < purpose >.

Eg.: As a performant website, I wish to embrace inline CSS for node X on web page template Y with a purpose to obtain the most important contentful paint for this web page template in below 2.5 seconds.

Acceptance Standards
Outline when the purpose has been achieved.  What does “completed” imply? Eg.:

• Inline any critical-path CSS used for above-the-fold content material by together with it instantly in <head>.
• Vital CSS (learn as: that associated to node X) seems above JS and CSS useful resource hyperlinks within the <head>.

Testing URLs/Technique
Embody the grouped instance URLs you copied down from Search Console. Present a set of steps for QA engineers to observe.
Take into consideration which instrument is used, what metric/marker to search for, and the habits indicating a move or fail.

Hyperlinks To Developer Doc
Use first-party documentation when obtainable. Please no fluffy blogs. Please? Eg.:

4. QA Modifications In Staging Environments Utilizing Lighthouse.

Earlier than code is pushed to manufacturing, it’s typically put in a staging atmosphere for testing. Use Lighthouse (by way of Chrome DevTools or native node occasion) to measure Core Internet Vitals.

For those who’re new to testing with Lighthouse, you possibly can find out about methods to check and testing methodology in A Technical search engine marketing Information to Lighthouse Efficiency Metrics.

Remember the fact that decrease environments usually have fewer assets and might be much less performant than manufacturing.

Depend on the acceptance standards to dwelling in on whether or not the event work accomplished met the duty given.

Largest Contentful Paint

Represents: Perceived loading expertise.

Measurement: The purpose within the web page load timeline when the web page’s largest picture or textual content block is seen throughout the viewport.

Key Behaviors: Pages utilizing the identical web page templates usually share the identical LCP node.

Aim: 75% of web page masses obtain LCP in < 2.5 seconds.

Accessible as: Lab and Area Knowledge.

What Can Be LCP?

The LCP metric measures when the most important textual content or picture ingredient within the viewport is seen.

Potential parts that may be a web page’s LCP node embrace:

1. <img> parts.
2. <picture> parts inside an <svg> tag.
3. poster pictures of <video> parts.
4. background pictures loaded by way of url() CSS perform.
5. Textual content nodes inside block-level parts.

Anticipate to see further parts like <svg> and <video> added in future iterations.

How To establish LCP Utilizing Chrome DevTools

1. Open the web page in Chrome emulating a Moto 4G.
2. Navigate to the Efficiency panel of Dev Instruments (Command + Possibility + I on Mac or Management + Shift + I on Home windows and Linux).
3. Hover over the LCP marker within the Timings part.
4. The ingredient(s) that correspond to LCP is detailed within the Associated Node subject.

What Causes Poor LCP?

There are 4 frequent points inflicting poor LCP:

1. Sluggish server response occasions.
2. Render-blocking JavaScript and CSS.
3. Sluggish useful resource load occasions.
4. Consumer-side rendering.

Supply points for LCP are painted in broad strokes at greatest. Sadly, not one of the single phrases above will probably be sufficient to move alongside to your dev group with significant outcomes.

Nevertheless, you can provide the problem momentum by homing in on which of the 4 origins is in play.

Bettering LCP goes to be collaborative. Getting it fastened means sitting in on dev updates and following up as a stakeholder.

Diagnosing Poor LCP As a result of Of Sluggish Server Response Time

The place to look: Crux Dashboard v2 – Time to First Byte (TTFB) (web page 6)

IF you see persistently poor TTFB in your subject information, then it’s sluggish server response time dragging LCP.

How To Repair Sluggish Server Response Time

Server response time is fabricated from quite a few components bespoke to the location’s know-how stack. There aren’t any silver bullets right here. Your greatest plan of action is to open a ticket together with your improvement group.

Some attainable methods to enhance TTFB are:

1. Optimize the server.
2. Route customers to a close-by CDN.
3. Cache property.
4. Serve HTML pages cache-first.
5. Set up third-party connections early.

Diagnosing Poor LCP As a result of Of Render-Blocking JavaScript And CSS

The place to look: Lighthouse (by way of net.dev/measure, Chrome DevTools, Pagespeed Insights, or nodeJS occasion). Every of the options under embrace a related audit flag.

How To Repair Render-blocking CSS

CSS is inherently render-blocking and affect important rendering path efficiency. By default, CSS is handled as a render-blocking useful resource.

The browser downloads all CSS assets, no matter blocking or non-blocking habits.

Minify CSS.

In case your website makes use of a module bundler or construct instrument, discover the plugin that may systematically decrease the scripts.

Defer non-critical CSS.

The Code Protection report in DevTools will assist you establish which kinds are used on the web page. If it’s not used on any pages, then take away it completely. (No judgement, CSS recordsdata can shortly bloat into the proverbial junk drawer.)
If the kinds are used on one other web page, make a separate model sheet for these pages which use it to name.

Inline important CSS.

Embody the critical-path CSS used for above-the-fold content material (as recognized by the Code Protection report) instantly in <head>.

Use Dynamic Media Queries.

Media queries are easy filters that when utilized to CSS kinds escape the kinds based mostly on the varieties of machine rendering the content material.

Utilizing dynamic media queries means as an alternative of calculating kinds for all viewports, you’re calling and calculating these values to the requesting viewport.

How To Repair Render-Blocking JavaScript

Minify and compress JavaScript recordsdata.
You’ll have to work with builders to minify and compress community payloads.

Minification entails eradicating unneeded whitespace and code. It’s greatest completed systematically with a JavaScript compression instrument.

Compression entails algorithmically modifying the info format for performant server and shopper interactions.

Defer unused JavaScript.
Code splitting chops up massive chunks of JS to ship smaller packages. You’ll be able to then load those who matter to above-the-fold content material first.

Reduce unused polyfills.
Keep in mind how Googlebot was caught in Chrome 44 for what felt like centuries? A polyfills is a chunk of code used to supply fashionable performance on older browsers that don’t natively assist it.

Now that Googlebot is evergreen, it additionally goes by the title tech debt.

Some compilers have built-in functionalities to take away legacy polyfills.

How To Repair Render-Blocking Third-Celebration Scripts

Delay it.

If the script doesn’t contribute to above the fold content material, use async or defer attributes.

Take away it.

If the script makes use of an <iframe> within the head, take away it. Contact the seller for an up to date implementation technique.

Consolidate it.

Audit third-party script use. Who’s answerable for the instrument? A 3rd-party instrument with out somebody managing it’s also often called a legal responsibility.

What worth does it present? Is that worth higher than the affect on efficiency? Can the consequence be achieved by consolidating instruments?

Replace it.

An alternative choice could also be to achieve out to the supplier to see if they’ve an up to date lean or asynchronous model. Typically they do and don’t inform people which have their previous implementation.

Diagnosing Poor LCP As a result of Of Sluggish Useful resource Load Occasions

The place to look: Lighthouse (by way of net.dev/measure, Chrome DevTools, Pagespeed Insights, or nodeJS occasion). Every of the options under features a related audit flag.

Browsers fetch and execute assets as they uncover them. Typically our paths to discovery are lower than ideally suited. Different occasions the assets aren’t optimized for his or her on-page experiences.

Listed below are methods you possibly can fight the most typical causes of sluggish useful resource load occasions:

1. Optimize and compress pictures.
   Nobody wants a 10MB png file. There’s hardly ever a use case for delivery a big picture file.  Or a png.
2. Preload essential assets.
   If a useful resource is a part of the important path, a easy rel="preload" attribute tells the browser to fetch it as quickly as attainable.
3. Compress textual content recordsdata.
   Encode, compress, repeat.
4. Ship completely different property based mostly on community connection (adaptive serving).
   A cell machine on a 4G community isn’t more likely to want/need/tolerate the loading time of property prepared for an extremely 4K monitor. Use the Community Info API which allows net purposes to entry details about the person’s community.
5. Cache property utilizing a service employee.
   Whereas Googlebot doesn’t execute service employees, a person’s machine on a thimble’s price of community connection actually will. Work together with your improvement group to leverage the Cache Storage API.

Diagnosing Poor LCP As a result of Of Consumer-Aspect Rendering

The place to look: For one-off glances, view the web page supply. If it’s a few traces of gibberish, the web page is client-side rendered.

Components inside a web page might be client-side rendered. To identify which parts, evaluate the preliminary web page supply with the rendered HTML. For those who’re utilizing a crawler, evaluate the rendered phrase depend distinction.

Core Internet Vitals are a means of measuring how efficient our rendering methods are.

All rendering choices have the identical output (all of them construct net pages), however CWV metrics measure how shortly we ship what issues when it issues.

Consumer-side rendering isn’t the reply until the query is, “What adjustments went into manufacturing on the identical time that natural site visitors started to tumble?”

How To Repair Consumer-Aspect Rendering

“Cease” actually isn’t a helpful reply. Correct, however not helpful. So as an alternative:

1. Reduce important JavaScript.
   Use code splitting, tree shaking, and inline capabilities within the head for above-the-fold functionalities. Maintain these inline scripts <1kb.
2. Use server-side rendering.
   By having your servers execute JS parts, you possibly can return totally rendered HTML. Notice that it will improve your TTFB because the scripts are executed earlier than your server responds.
3. Use pre-rendering.
   At construct time, execute your scripts and have rendered HTML prepared for incoming requests. This selection has a greater server response time however received’t work for websites with steadily altering stock or costs.

To be clear: Dynamic rendering is just not an answer to client-side rendering. It’s giving the troubles of client-side rendering a pal.

First Enter Delay (FID)

Represents: Responsiveness to person enter.

Measurement: The time from when a person first interacts with a web page to the time when the browser is definitely in a position to start processing occasion handlers in response to that interplay.

Key behaviors: FID is simply obtainable as subject information.

Aim: 75% of web page masses obtain FID in <= 100 milliseconds.

Accessible as: Area Knowledge.

Use Whole Blocking Time (TBT) For Lab Assessments

Since FID is simply obtainable as lab information, you’ll want to make use of Whole Blocking Time for lab assessments. The 2 obtain the identical finish consequence with completely different thresholds.

TBT represents: Responsiveness to person enter.

TBT measurement: Whole time by which the principle thread is occupied by duties taking greater than 50ms to finish.

Aim: <= 300 milliseconds.

Accessible as: Lab Knowledge.

What Causes Poor FID?

const jsHeavy = true;
    Whereas (jsHeavy) {
        console.log("FID fail")
    }

Heavy JavaScript. That’s it.

Poor FID comes from JS occupying the principle thread which suggests your person’s interactions are pressured to attend.

What On-Web page Components Are Impacted By FID?

FID is a means of measuring most important thread exercise. Earlier than on-page parts can reply to person interplay, in-progress duties on the principle thread have to finish.

Listed below are a number of the most prevalent parts that your person is tapping in frustration:

1. Textual content fields.
2. Checkboxes.
3. Radio buttons (<enter> and <textarea>).
4. Choose dropdowns (<choose>).
5. Hyperlinks (<a>).

The place to look: To verify it’s a difficulty for customers have a look at Crux Dashboard v2 – First Enter Delay (FID) (web page 3). Use Chrome DevTools to establish the precise duties.

How To See TBT Utilizing Chrome DevTools

1. Open the web page in Chrome.
2. Navigate to the Community panel of Dev Instruments (Command + Possibility + I on Mac or Management + Shift + I on Home windows and Linux).
3. Tick the field to disable cache.
4. Navigate to the Efficiency Panel and verify the field for Internet Vitals.
5. Click on the reload button to begin a efficiency hint.
6. Search for the blue blocks labeled Lengthy Duties or the pink proper nook markers within the right-hand nook of duties. These point out lengthy duties that took greater than 50ms.
7. Discover the TBT for the web page on the backside of the abstract.

How To Repair Poor FID

Cease loading so many third-party scripts.

Third-party code places your efficiency behind one other group’s stack.

You’re depending on their scripts executing in a succinct, performant method to ensure that your aspect to be thought of performant.

Unlock the principle thread by breaking apart Lengthy Duties.

For those who’re delivery one large JS bundle for each web page, there’s lots of functionalities in that bundle that don’t contribute to the web page.

Though they’re not contributing, every JS perform must be downloaded, parsed, compiled, and executed.

By breaking out that large bundle into smaller chunks and solely delivery those who contribute, you’ll liberate the principle thread.

Examine your tag supervisor.

Out-of-the-box tag deployment of tags hearth occasion listeners that may tie up your most important thread.

Tag managers might be long-running enter handlers that block scrolling. Work with builders to debounce your enter handlers.

Optimize your web page for interplay readiness.

Ship and execute these JS bundles in an order that issues.

Is it above the fold? It will get prioritized. Use rel=preload.

Fairly essential however not sufficient to dam rendering? Add the async attribute.

Under the fold? Delay it with the defer attribute.

Use an internet employee.

Internet employees permit JavaScript to run on a background thread quite than the principle thread your FID is scored on.

Scale back JavaScript execution time.

For those who’re delivery one large JS bundle for each web page, there’s lots of functionalities in that bundle that don’t contribute to the web page.

Though they’re not contributing, every JS perform must be downloaded, parsed, compiled, and executed.

By breaking out that large bundle into smaller chunks (code splitting) and solely delivery those who contribute (tree shaking), you’ll liberate the principle thread.

Cumulative Format Shift

Represents: Visible stability.

Measurement: A calculation based mostly on the variety of frames by which ingredient(s) visually strikes and the overall distance in pixels the ingredient(s) moved.

structure shift rating = affect fraction * distance fraction

Key behaviors: CLS is the one Core Internet Very important not measured in time. As a substitute, CLS is a calculated metric. The precise calculations are actively being iterated on.

Aim: 75% of web page masses have a CLS calculated metric of >0.10.

Accessible as: Lab and Area Knowledge.

Diagnosing Poor CLS

The place to look: To verify it’s a difficulty for customers have a look at Crux Dashboard v2 – Cumulative Format Shift (CLS) (web page 4). Use any instrument with Lighthouse to establish the bouncing ingredient(s).

Chrome DevTools will present higher insights into the coordinates of the excitable ingredient and what number of occasions it strikes.

How To See CLS Utilizing Chrome DevTools

1. Open the web page in Chrome.
2. Navigate to the Community panel of Dev Instruments (Command + Possibility + I on Mac or Management + Shift + I on Home windows and Linux).
3. Tick the field to disable cache.
4. Navigate to the Efficiency Panel and verify the field for Internet Vitals.
5. Click on the reload button to begin a efficiency hint.
6. Click on on the pink marker(s) within the Expertise part.
7. Search for the title of the node, highlighting of the node on web page, and the coordinates for every time the ingredient moved.

What Can Be Counted In CLS?

If a component seems within the preliminary viewport, it turns into a part of the metric’s calculation.

For those who load your footer earlier than your main content material and it seems within the viewport, then the footer is a part of your (probably atrocious) CLS rating.

What Causes Poor CLS?

Is it your cookie discover? It’s in all probability your cookie discover.

Alternatively, search for:

1. Pictures with out dimensions.
2. Advertisements, embeds, and iframes with out dimensions.
3. Dynamically injected content material.
4. Internet Fonts inflicting FOIT/FOUT.
5. Chains for important assets.
6. Actions ready for a community response earlier than updating DOM.

How To Repair Poor CLS

At all times embrace width and peak measurement attributes on pictures and video parts.

It’s so simple as <img src="https://www.searchenginejournal.com/technical-seo-core-web-vitals-guide/402501/stable-layout.jpg" width="640" peak="360" /> but additionally not. Responsive net design noticed the decline of peak and width declarations. The unfavorable affect of that is pages reflowing as soon as the picture appeared on display screen.

Greatest follow is to leverage user-agent stylesheets for systematically declared dimensions based mostly on the picture’s side ratio.

Reserve area for advert slots (and don’t collapse it).

For those who’re a publishing website, you’re by no means going to win an argument over the unfavorable efficiency affect of third-party adverts.

As a substitute, establish the most important measurement advert that could possibly be utilized in a slot and reserve area. If the advert doesn’t populate, maintain the placeholder. The hole is best than a structure shift.

Keep away from inserting new content material above present content material.

A component shouldn’t enter the preventing area until it’s able to be counted.

Take care when putting non-sticky adverts close to the highest of the viewport.

As a common rule, keep away from adverts close to the highest of the web page. You’ll probably see these flagged within the new GSC Web page expertise report.

Preload fonts and demanding assets.

A font loading late causes a full flash and re-write.

Preload tells the browser that you just want to fetch it before the browser would in any other case uncover it since you are sure that it is vital for the present web page.

<hyperlink rel="preload" href="https://www.searchenginejournal.com/property/Pacifico-Daring.woff2" as="font" sort="font/woff2" crossorigin>

Keep away from chains for assets wanted to create above-the-fold content material.

Chains occur whenever you name a useful resource that calls a useful resource. If a important asset is named by a script, then it may’t be referred to as till that script is executed.

Keep away from doc.write()

Trendy Browsers assist speculative parsing off of the principle thread.

Learn as: They work forward whereas scripts are being downloaded and executed – like studying forward of assignments in a category. doc.write() is available in and adjustments the textbook. Now that work studying forward was ineffective.

Chances are high this isn’t the work of your devs. Speak to your level of contact for that “magic” third-party instrument.

The Future Of CWV Metrics

Google intends to replace the Web page Expertise parts on an annual foundation. Future CWV metrics might be documented equally to the preliminary sign rollout.

Think about a world the place search engine marketing professionals received discover a yr upfront that Panda was coming!

Core Internet Vitals are already 55% of your Lighthouse v7 rating.

At present, Largest Contentful Paint (LCP) and First Enter Delay (FID) are every weighted at 25%. Cumulative Format Shift is a meager 5% however we will count on to see these equalize.

Good cash is on This autumn 2021 as soon as the Chromium group hones within the metric’s calculation.

As technical search engine marketing execs, we’re in a position to diagnose and supply options for a greater user-centric expertise. Right here the factor – these investments and enhancements affect all customers.

The ROI might be present in each medium. Each channel.

Natural efficiency is an general reflection of website well being. Leverage that place as you proceed to advocate and iterate. Share what you be taught.

Most significantly:

|￣￣￣￣￣￣￣￣￣￣￣|
Don’t be afraid to
be taught in public
|＿＿＿＿＿＿＿＿＿＿＿|
(__/) ||
(•ㅅ•) ||
/ 　 づ

---

2021 SEJ Christmas Countdown:

Picture Credit

Featured picture: Piscine26/Shutterstock
All screenshots taken by creator