Google’s Core Web Vitals Update: How to Adjust for SEO Success

Ruthie Careyby Ruthie Carey

Home | Blog | Google’s Core Web Vitals Update: How to Adjust for SEO Success

Share this article

It’s almost here.

For those who haven’t been following the story, back in May of 2020, Google published a blog on evaluating page experiences that announced it would be “providing an early look at an upcoming Search ranking change that incorporates” the recently announced Core Web Vitals metrics.

May 2021 is nearly upon us, which means that it is time for this Google algorithm update to go into effect, thereby impacting the rankings of many.

We say this because Google has given sellers an entire year’s notice on this algorithm change – a far cry from the norm – which means that the impact could potentially be significant.

The new performance metrics that Google will be integrating, officially dubbed Core Web Vitals, will become a deciding factor in search rankings starting in Q2 of this year. Moreover, this change will apply across the board. It matters not if a site is a publisher of news articles or an online retail shop – the Core Web Vitals update will touch all sites.

This is a big deal since organic search is one of the most effective ways for consumers to discover eCommerce retailers. Moreover, SEO takes time to produce results, meaning this update could set some merchants back in a significant way.

Given that many brands are scared about taking a hit to their SEO performance as a result of the new Core Web Vitals update, scores of sellers have been busy optimizing their websites for the switch. However, given that there is a lot that goes into producing a stellar user experience that is not reflected in Google Core Web Vitals, many are feeling the frustration.

Therefore, as a means of helping retailers navigate this UX-related algorithm update and helping clients and followers understand what Visiture is doing to minimize the impact of the update and keep organic traffic levels high, today, we will be exploring the Core Web Vitals update, its implications, whom it could affect and how we are managing the situation.

With that said, let’s start by discussing exactly what Core Web Vitals are and what goes into these metrics.

What Are Core Web Vitals?

For those who are unaware, Core Web Vitals are a set of factors that Google deems to be essential in the overall user experience of a website.

As it stands, Core Web Vitals consist of three page speed and user interaction calculations. Those three measurements are:

  • Largest Contentful Paint (LCP): This is essentially akin to website latency
  • Cumulative Layout Shift (CLS): A measurement of page layout constancy versus change
  • First Input Delay (FID): This metric measures interactivity.

In sum, Core Web Vitals will ultimately become a part of Google’s page experience score, which is basically a way for Google to gauge a page’s overall user experience.

The page experience signal will now integrate Core Web Vitals with the following signals:

With this outlined, it is essential to note that an amazing user experience alone isn’t going to push a site to the top of the SERPs. In fact, this is something that Google was quick to acknowledge as page experience is only one of over 200 ranking factors.

That is the Core Web Vitals in a nutshell.

Now, let’s get into the weeds a bit and gain a more comprehensive understanding of LCP, CLS, FID and how this Google algorithm update is going to impact sellers.

What is Largest Contentful Paint (LCP)?

LCP, which stands for Largest Contentful Paint, is a metric that measures the execution time of the most prominent text block or image present within a viewport.

For those that are unaware, the viewport is the user’s visible area of the webpage.

The new LCP metric is fantastic for a number of reasons.

First, before LCP came into existence, many developers found it extremely challenging to establish how quickly the elements on their main web pages loaded and when they became visible to site visitors. Meanwhile, older metrics like DOM ContentLoaded or load time were relatively inadequate as they didn’t always sync with what users would see on their end. Moreover, metrics like FCP (First Contentful Paint) were only capable of capturing the initial stages of the loading experience.

Prior to LCP, much emphasis was placed on analyzing KPIs in Google Lighthouse like Speed Index and First Meaningful Paint as these could help to capture more of the loading experience than FCP could manage. However, the problem with these metrics is that they are pretty complex, challenging to explain, and often inaccurate. In the end, this means that the aforementioned metrics were insufficient for identifying when the primary content of a page loaded.

As a result of these issues, Google research sought to establish a more accurate way of gauging when a page loaded its main content, ultimately discovering that the best gauge was when the biggest element was executed.

Understanding this, LCP is the new metric that is capable of capturing the loading speed of the elements of a web page that are visible to site visitors, be they text, images, videos, GIF, or another asset.

As far as scoring is concerned, LCP is scored in three ranges:

  • Good
  • Needs improvement
  • Poor

As far as improving SEO rankings through Core Web Vitals is concerned, LCP (and the other two yet-to-be discussed rankings) must fall within a specific window of acceptability that Google has defined as:

  • Good: Less than or equal to 2.5 seconds
  • Needs improvement: Less than or equal to four seconds
  • Poor: Greater than four seconds

This means that in order to benefit from the LCP metrics, a seller’s page must display its most sizable element within 2.5 seconds of a user landing on the destination.

As of this writing, the elements measured are restricted to text and images. However, in the future, it is extremely likely that video will be factored into the LCP metric.

What is Cumulative Layout Shift (CLS)?

Cumulative Layout Shift (CLS) measures the sum total of all individual layout shift scores for each of the unexpected layout shifts that take place over the entire lifespan of the page.

Such shifts take place when visible on-page elements change position from one of the rendered frames onto the next. As a result, web development teas are constantly aiming to improve their site’s layout performance by fixing bugs, altering experience page weight and analyzing unexpected layout shifts.

These kinds of unexpected movements tend to occur when resources load in an asynchronous manner or when DOM elements are added to a page dynamically, over-and-above existing content. As a result, fonts might render smaller or larger, videos or images might have unknown dimensions or a similar situation.

CLS serves to quantify unpredicted layout shifts that take place. Therefore, Cumulative Layout Shift can be a great tool in helping to address these issues as this metric is quite effective in detecting how often shifts occur for end users.

However, much like with LCP, a seller’s pages must fall within a narrow window of acceptability to reap the eCommerce SEO benefits that can be gained from Core Web Vitals becoming a ranking factor.

CLS uses a formula that generates a decimal value that effectively measures the total amount of unexpected shifts that occur on a site. As with LCP, Google scores CLS in three ways:

  • Good: Less than or equal to 0.1
  • Needs improvement: Less than or equal to 0.25
  • Poor: Greater than 0.25

As can be seen, the lower the CLS score, the better the page is performing. That said, CLS scores are not as intuitive as some of the other Core Web Vital KPIs. In order for retailers to properly understand their CLS scores, it is necessary to grasp the formula used to arrive at this number.

To generate a page’s CLS score, sellers must multiply two figures. The first one is called the impact fraction – a number that represents how much space a shifting element takes up on the screen. The second number is called the distance fraction. The distance fraction serves to show how much a shifting element moves. Multiplying these two numbers will enable sellers to find their layout shift score.

However, do keep in mind that layout shift scores are different from Cumulative Layout Shift, as the latter is representative of the sum of all shifting that takes place on a page.

So, with this understanding, CLS essentially means the more space-shifting elements take up, the bigger the problem sellers are facing. Moreover, the larger the distance elements move, the larger the problem.

What is First Input Delay (FID)?

First Input Delay, or FID for short, helps merchants to measure the first impression users receive of the site’s responsiveness and interactivity. FID calculates the time from when a user initially interacts with a web page (tapping a button, clicking a link, etc.) to the time when the browser is capable of processing event handlers in response to the interaction.

Generally speaking, input delay or input latency happens as a result of a browser’s main thread being preoccupied with a different task, thereby making it incapable of immediately responding to the user.

A common reason as to why this might occur is that the browser is engaged in parsing and executing a sizable JavaScript file loaded by a merchant’s page. While this is going on, the browser cannot run any event listeners as the JavaScript its loading could be telling it to do something else.

Long FIDs tend to take place between First Contentful Paint and Time to Interactive as the page has successfully rendered some of its content but is not yet reliably interactive.

As with the previous two metrics, Google scores FID in three different categories:

  • Good: Less than or equal to 100 milliseconds
  • Needs improvement: Less than or equal to 300 milliseconds
  • Poor: Greater than 300 milliseconds

What this means is that when a visitor to a page initially attempts to interact with the site, the website must respond to that interaction within 100 milliseconds for FID to contribute to improving a site’s rankings.

However, it is important for merchants to remember that a good FID scoring does not mean that a site must fully load within 100 milliseconds. The total load time is an entirely different metric that is not a part of Core Web Vitals.

That said, the faster a retailer’s site load and the more efficiently their server and code are working on loading the store, the more likely it is that a seller will achieve an ideal FID score.

With the Core Web Vital metrics covered in detail, let’s go ahead and take a moment to explore Google’s reasoning for implementing this algorithm change.

The Rationale Behind Core Web Vitals

Ultimately, as is the intention of most of Google’s changes, the company aims to help users obtain better search results. In this particular case, Google is achieving this by understanding which websites produce the best possible experience for users.

In the end, Core Web Vitals serve to more closely integrate SEO and UX optimization. After all, if a website has all of the information or products that a consumer is seeking but has an atrocious on-site interface, can the experience really be called good?

Through this algorithmic update, Google is telling merchants that their site not only needs to cater to user intentions, be authoritative, trustworthy, and be optimized on its backend, but it must also ensure that its speed, interactivity, responsiveness, mobile-friendliness and the like must be outstanding as well.

Additionally, as far as retailers and web admins are concerned, this change is one that should be welcomed as quantifying user experience metrics has been incredibly challenging up to this point. Prior to these metrics, understanding and analyzing user experience enhancements has primarily been a subjective process.

However, through the implementation of Core Web Vitals, merchants have the tools to better understand (and thus improve) user experiences as real-world data from site visitors can help to guide the process.

That said, this update is not all upside as there are certain types of sites that this alteration could impact more than others.

Who Will Be Impacted Most?

The fact of the matter is that the Core Web Vitals update is going to affect all of the sites using Google. Moreover, this update will impact the SERPs for mobile and desktop, as well as become a key component for appearing in Google Top Stories.

While this is a bit of a sidebar, it is important to note as it could affect rankings. While AMP was once a requirement for landing in Top Stories, that qualifier is now going away. As Google stated in its timing for page experience signals announcement:

“The change for non-AMP content to become eligible to appear in the mobile Top Stories feature in Search will also roll out in May 2021. Any page that meets the Google News content policies will be eligible and we will prioritize pages with great page experience, whether implemented using AMP or any other web technology, as we rank the results.”

With that aside covered, it is crucial to understand that if a site isn’t up to snuff as far as Core Web Vitals are concerned, it will be vital for merchants to improve performance.

That means that there are both technological and budgetary issues with which site owners will need to grapple. That said, some of the sites that could find the Core Web Vitals update to be less favorable include:

Sites Using a CMS

A traditional CMS that employs a database can be a bit of a complex case given that the overhead from executing queries and other functions is going to slow the site down overall. In this case, caching can help, but there will likely need to be additional implementations to bring the site up to Google’s standards.

When looking to improve a site’s speed, features like a content delivery network or premier hosting service could be necessary to push the site’s load times to acceptable levels.

However, even in this instance, excess plugins, bloated themes, or a number of other issues could still hold the site back from reaching higher potentialities. For example, the WordPress theme market is notorious for housing scores of heavy choices.

In this case, one of the more viable options for developers to bring the site up to Google’s expectations is by switching themes, eliminating plugins, or opting to employ a headless commerce configuration as decoupling the front and backend could speed the site up enough to pass muster.

Sites Utilizing Out-of-the-Box Solutions

Retailers that opt for eCommerce solutions like Wix, Squarespace, and similar options may find that they do not have the tools or access necessary to remedy all of their performance problems.

The fact of the matter is that many out-of-the-box eCommerce software solutions only enable users to tweak certain aspects of their site, leaving more technical aspects wholly gated off from accessing.

Moreover, when it comes to server infrastructure, there is really nothing to be done for those utilizing a hosted platform. While there might be the potential for an account level upgrade, it is likely that merchants will want to upgrade their eCommerce platform to gain access to additional or better resources.

However, this is not a viable option for some sellers, which brings us to our last potentially heavily impacted site type.

Sites Without an Optimization Budget

The reality of the situation is that improving site performance requires time and money to achieve. While it is a critical investment given that SEO is vital to scaling a business, the fact is that certain optimization projects could be out of reach for those operating on razor-thin margins.

Part of the reason for this is that, when optimizing an eCommerce website, there are a variety of facets that must be explored. Some retailers will need images optimized, while others need their code to be retooled. Depending on the situation, the optimization investment could vary greatly.

For those that need a multitude of things done to ensure their site performance aligns with the Core Web Vitals demands might find that the cost for the work can add up quickly. In fact, in this type of situation, it might be best for sellers to scrap their site and opt to start from scratch with a complete Commerce Transformation.

Similarly, web hosting could also play a major role for low-budget websites as they might not have enough server resources. Again, upgrading a merchant’s hosting service will require funds to achieve.

Will the Impact of the Core Web Vital Update Be Significant?

Coming off the tails of the previous section, the answer here is a resounding:

It depends.

Firstly, it is essential to keep in mind that Google has hundreds of different ranking factors. Therefore, the impact of a single signal is not usually massive. With that said, if a merchant’s site is vastly underperforming in some of the previously covered metrics, this update could have a substantial impact.

That said, some signals can have a disproportionate impact when compared to the weight that Google assigns them. For instance, signals like speed may not be super heavily weighted. However, the way that speed influences the user experience could result in higher bounce rates, fewer conversions, fewer page views, and produce other signs that Google will perceive as negative.

For instance, Google studies on Web Vitals have shown a substantial impact on site abandonment. As the study detailed:

“We analyzed millions of page impressions to understand how these metrics and thresholds affect users. We found that when a site meets the above thresholds, users are 24 percent less likely to abandon page loads (by leaving the page before any content has been painted). We also looked specifically at news and shopping sites, sites whose businesses depend on traffic and task completion, and found similar numbers: 22 percent less abandonment for news sites and 24% less abandonment for shopping sites.”

What this means is that even if Core Web Vitals were not becoming a ranking factor, the metrics which it measures are still vital to the overall user experience and site performance.

At the same time, the competitiveness of a seller’s niche also plays a role. For those that are in a highly competitive environment, it is wise to expect rivals to be doing all they can to gain a competitive edge at this moment. For those that don’t take the update seriously, the impact could be severe.

However, for those that are not in a cutthroat area of commerce, this could be less of a concern.

How to Measure and Correct Issues

With a current understanding of what the Core Web Vitals update is, why Google is doing it, who will likely be impacted the most and how seriously others should take the alteration, let’s turn our attention to how to measure Core Web Vitals and how to fix any potential issues that merchant might be facing.

Thankfully, Google has made measuring Core Web Vitals performance quite simple. The first thing sellers will want to do is access the Search Console. Here, retailers will find that Google has added a new report called Core Web Vitals.

How convenient.

Accessing this report will show sellers all of their URLs that are indexed and how they are performing (good, needs improvement or poor). For those URLs that show “poor” or “need improvement,” retailers will want to investigate those pages and find out what is potentially causing them to be scored in such a way.

Moreover, since every report in Search Console links to a report in PageSpeed Insights, this is likely where retailers will want to turn first to diagnose Core Web Vitals issues.

For those who are unaware, PageSpeed is powered by Lighthouse, which is a more extensive suite of metrics tools for measuring the quality of web pages.

As a bit of a forewarning, some of the information presented by Lighthouse can get quite technical. Therefore, it is advisable to hire a web developer who is well-versed in page speed management.

That said, merchants will want to go through and address each of the diagnostics as a means of enhancing Core Web Vitals scores and improving any page that is not rated as “good.”

With this understanding of how to access Core Web Vitals scoring covered, let’s now turn to what Visiture is doing to help our clients enhance their site speed, user experience and maintain healthy traffic levels during the Core Web Vitals update.

How Visiture is Handling the Core Web Vitals Update

As was just discussed, since Core Web Vitals can be accessed through the Search Console, knowing what needs to be improved is pretty simple. However, understanding how to improve those issues is more complex.

Therefore, specific page speed audits need to be completed to understand precisely what’s causing existing issues and how to remedy any problems.

While the specifics will vary between eCommerce websites, here is some general advice for improving Core Web Vitals scores:

Improving LCP

As it stands, LCP is currently weighted as 25 percent of the Lighthouse audit score. Therefore, enhancing LCP load times is critical to success.

As discussed earlier, LCP measures the elements rendered in the user’s viewport. The fact that this is being measured continues to underline a point that has been made by developers and marketers for many years: The importance of the elements that live above the folks and the necessity of their ability to load quickly.

However, the particularly challenging part about this is that the viewport is likely to change for nearly all users as the dimensions of their device’s screen will vary from user to user. Therefore, one of the first steps to optimizing LCP scores is to know what viewport sizes a seller’s audience is using.

Merchants can uncover this information by going to Google Analytics and navigating to Audience > Mobile > Overview. To discover the viewport size, sellers will want to include a secondary dimension of browser size. Similarly, merchants can establish the same information for desktop users by searching the word “desktop” and viewing the browser sizes for those folks.

Once merchants know the viewport sizes of their user base, they can focus on optimizing their site speed for those specific device dimensions by pinpointing the largest element within those viewport sizes.

As far as retailers are concerned, eCommerce product pages that are reported as having a slow loading LCP, the issue is almost always the main product image. Similarly, on static pages, the problem is almost always the hero or banner image.

In these cases, optimizing those images to the full extent or preloading these images can have a massive impact on the time taken to load these assets, thereby fixing any issue reported in Search Console that could directly impact organic performance.

Some other potential tactics that sellers can use to improve LCP include:

  • Eliminate unnecessary third-party scripts
  • Upgrade web hosting providers
  • Remove large page elements where possible
  • Minify CSS

Sellers could also opt to set up lazy loading. However, this could potentially cause issues with Cumulative Layout Shift scores. Therefore, if merchants choose to go this route, it is also essential to implement strategies for preventing content reflow from lazy-loaded images.

Improving CLS

Layout shift tends to occur when images have no height or width associated and can be caused by lazy loading responsive images. Again, there are tactics sellers can implement to mitigate this issue.

Another potential solution for enhancing CLS is to utilize placeholders for shifting elements.

For instance, if merchants have a slow-loading ad that appears on their page from a third party and that advert tends to cause things to shift down the page when it finally does fully load. This happening could result in a high distance score as it ultimately pushes other elements down the page. In turn, this results in a CLS score of “needs improvement” or even “poor.”

Instead of removing the ad (thus losing revenue), site owners could instead opt to implement placeholders to allow space for the element. This way, when the ad loads, instead of shifting other elements down the page, it will instead occupy the empty space created by the placeholder.

While this tactic may not be a viable solution for all or even for all instances, it is a potentially simple solution for enhancing a page’s CLS score.

Alternatively, some other methods that merchant might use to minimize CLS include:

  • Using set size attributes for all media implementations
  • Ensure that ad elements have a reserved space on a page
  • Include interface elements below the fold

Improving FID

For sellers to reduce FID, their website must quickly respond when a visitor attempts to interact with specific site elements. However, be aware that this does not mean that web stores need to complete the requested task fully. Instead, a site should respond with some type of affirmation that the user’s interaction is being responded to and processed.

For instance, if a user clicks a CTA, a popup with a loading icon might materialize within 100 milliseconds.

The fact of the matter is that what FIC is analyzing is the ideal time within the main thread. The main thread is representative of everything the browser is processing in terms of website events. When a user interacts with the site, that interaction is processed on the main thread.

When a site is poorly optimized, the main thread can quickly become backlogged with so many tasks that it is unable to respond to user interactions rapidly.

For instance, if the main thread is preoccupied loading files and executing a JavaScript function that will take approximately 400 milliseconds, those tasks will block anything else from being loaded until they are complete. This means that if a user interacts with the site when the tasks begin, they will be waiting for more than 400 milliseconds for the site to respond to their request.

Therefore, when focusing specifically on FID, looking at breaking up long tasks into smaller, asynchronous ones can allow user input between the tasks. This means that merchants will need a lot of idle time in their main thread. Achieving this aim is dependent upon optimizing JavaScript files and strategically mapping out when certain things should load.

Moreover, sellers will need to optimize CSS and defer non-critical CSS so that it doesn’t preoccupy the main thread, thereby allowing the site to respond to user interactions quickly.

Some other tactics merchants can use to improve their FID scoring include:

  • Defer unused JavaScript and anything else not critical to page performance
  • Always push for server-side rendering instead of client-side rendering
  • Eliminate non-critical third-party scripts
  • Employ a browser cache

Moreover, while all of these LCP, CLS, and FID solutions can help retailers to optimize their site’s speed and user experience, there are other alternatives to be considered.

PWAs: A Viable Core Web Vitals Solution

Core Web Vitals is focused on propping up sites that are fast and promote a fantastic user experience. Moreover, Google as a whole has been pushing in a mobile-first direction for many years now.

This is evidenced by the company’s creation of AMP, its 2016 decision to slowly begin implementing mobile-first indexing, which led up to zero desktop content in March of 2021, and a number of other determinations and initiatives that revolve around small screen devices.

The reasoning behind this push toward mobile is fairly apparent considering that, as Statista mobile internet data reveals:

“In 2020, the number of unique mobile internet users stood at 4.28 billion, indicating that over 90 percent of the global internet population use a mobile device to go online. Mobile ownership and internet usage are forecast to increase in the future, as mobile technologies are becoming more affordable and available than ever… Today, mobile internet traffic accounts for more than 55 percent of total web traffic, while in mobile-first markets such as Asia and Africa, mobile connections account for an even larger share of web page views.”

As far as online retailers are concerned, what this essentially means is that the best way to outperform competitors online and in the SERPs is to present users with an outstanding mobile experience.

As it stands, progressive web apps are redefining the mobile experience, giving users access to app-like interfaces without sacrificing discoverability through Google or other search engines.

For those who are unfamiliar, progressive web apps (PWAs) are a web development approach that utilizes cutting-edge technologies and tactics to produce mobile-first web experiences that look, feel and behave like applications but are still capable of being accessed like a traditional website as well.

The fact of the matter is that PWAs are a game-changer for eCommerce brands. The benefits provided by this technology are immense and have proven to be a powerful force of elevating user experience, improving load times, enhancing conversion rates, and generating high revenues for retailers.

There are tons of benefits to integrating PWA technology into a merchant’s technology stack. Some of the most notable and relevant perks for the Core Web Vitals discussion include:

Dramatically Reduced Load Times

Progressive web applications feature immensely faster load times than standard websites. The reason for this is that PWAs utilize device-level caching. This feature effectively reduced the data required to respond to user requests.

At the same time, Visiture builds PWAs using a headless architecture that separates the frontend from the backend. This architecture serves to allow sellers to create a data cache that enables stores to load content faster than even traditional applications.

Highlighting these effects, a 2016 Flipkart case study by Google displayed that, by adding services workers to the company’s PWA, Flipkart was able to speed up the on-site experience, thus increasing time on site threefold.

Similarly, sites like George.com were able to generate 3.8 times faster average load times on pages, thereby generating a 20 percent lift in pageviews per visit and 28 percent longer average time on site.

However, these benefits aren’t merely reserved for eCommerce retailers. As Think with Google reported on mobile site speed importance in 2019:

“BMW supercharged its website using AMP and Progressive Web Apps (PWA) — state-of-the-art technology for reliable, smooth, and secure web experiences that respond quickly to user interactions, even under poor network conditions. And what happened next? The proportion of people clicking from BMW.com to a BMW sales site soared from 8 percent to 30 percent, nearly 4X higher than before.”

The bottom line here is that PWAs are fast.

Like, really fast.

Enhanced User Experiences

Aside from how fast load times positively impact the user experience of a site, PWAs bring tons of other personalization features to the table.

For instance, PWAs users get to enjoy a myriad of micro-interactions and similar UI elements like those that are found in a multitude of applications. Moreover, thanks to the headless nature of PWAs, sellers can freely experiment with implementing new micro-interactions or features without being concerned about slowing the site down or interrupting a user’s experience.

This means that retailers can implement increasingly personalized experiences, thereby creating exponentially more engaging on-site interactions that will keep users coming back time and again.

In fact, since PWAs allow for brands to utilize push notifications, sellers can continually bring shoppers back on site since shoppers who enable push notifications have shown to produce 88 percent more app launches and three times higher retention rates.

Increased Site Security

Security is an issue that no merchant should take lightly. As it stands, it seems that every year, cybersecurity breaches get progressively worse.

Thankfully, progressive web applications provide retailers with increased security measures. Not only is the ever-necessary HTTPS protocol standard for PWAs, but thanks to the headless architecture used to create progressive web apps, the frontend and backend separation also serves to enhance on-site security, making merchants much less likely to fall victim to a DDoS attack.

Similarly, headless architecture also helps to guard against one of the most common website hacking schemes – SQL injections. Through this structure, the potential for an SQL injection is removed.

Maintained Discoverability

As mentioned earlier, one of the best parts of PWA implementation is that even though the technology acts as an application, it is still discoverable through Google and other search engines.

What this ultimately means is that potential buyers can gain access to a seller’s site as they normally would, but they will be provided with a far greater experience than most site owners could dream of producing through their traditional website.

Quick Creation and Delivery

While all of this sounds fantastic, it is somewhat useless in the context of the Core Web Vitals discussion if merchants can’t launch their PWA for six to nine months.

That said, another beautiful aspect of PWAs is that sellers can have them built much faster than a standard application.

In addition to PWAs being faster to produce, they are also easier to maintain as they tend to demand fewer continuous development requirements.

Therefore, if retailers are interested in having a PWA developed for their brand, the time to act is now.

Final Thoughts

Like it or not, the Core Web Vitals update is happening.

While it often seems like the moment webmasters and site owners think they know what Google wants, the company turns around and changes up the game.

However, as far as Core Web Vitals is concerned, Google has long been touting the importance of speed and user experiences in relation to SEO rankings and performance. This update only concretizes some of the more informal aspects of SEO that already existed.

The plain fact of the matter is that Google wants to see excellent website performance because that is what its users want from the results pages. However, actually implementing the changes necessary to produce the kind of experience that Google wants is going to take some experience and know-how to achieve.

That said, if your site wants to ensure that it is operating at its zenith and that it minimizes any potential ramifications that could come as a result of the Core Web Vitals update, then reach out to Visiture’s eCommerce SEO specialists.

Recent Updates From Google

June 30th – After Google delayed the initial core update rollout, users began to experience the release on June 2nd and saw it extend over the course of 10 days. With much volatility occurring throughout the process, Google revealed more uncertainty to come with a second portion of updates approaching in July.

Google announced that many features of the core update weren’t ready for release, therefore splitting the first half of the features in the June update with the second half expected to arrive in July.

According to Google, this second release could revert any changes experienced with the first release, leaving many sites wondering how they will be affected.

July 12th – As of July 12th, Google has confirmed the rollout of the July 2021 core update is complete. The second part of the core update rollout occurred between July 1st and July 12th, and according to data analysts, had much smaller effects than the core update in June.

If you experienced a severe rankings drop over the course of this update, Visiture’s team of experienced SEO professionals is prepared to advise on steps for recovery. We can ensure that your site is optimized for algorithm updates to come and offer related SEO guidance for your brand’s organic success.

Join 150+ Leading eCommerce Brands

And see how Visiture can grow your revenue online through award-winning transactional focused marketing services.

Stop Waiting!

Receive a Free eCommerce Marketing Audit Today!

Audit Emails

  • Submit Email

Popular Articles.

Data-Driven Marketing + Creative Commerce = Results.

Let’s Bring Our Teams Together and Connect You to Your Ideal Customer.