Did you upgrade your analytics property from UA to GA?
There was a bug in Enfold cookie popups a while ago but that was only if you had cookie consent enabled.
I had several sites stop recording until the bug fix came out.

I can think of five things that might have caused the failure to report traffic.

Your site/server had an error stopping visitors reaching the site
(having not seen the site) If the site has speed issues – visitors may have left before the cookies and analytics were processed.
The version of Enfold running contained the cookie consent popup bugs
WP-Rocket is set to defer inline JS then that would stop the Cookie consent working and stop analytics.js and gtag.js running.
Google analytics outage

Other than that – If traffic reports appear back to normal now then the problem is resolved

@adibranch
Assuming there is no problem with your tracking methods: This is one of the many pitfalls of Cookie Consent Policies required under EU Data Protection Laws.

If you serve customers in the area covered by GDPR then you are supposed to ask users to accept tracking cookies to be compliant. You should not load Google Analytics by default.

If you operate in the USA or other parts of the world where GDPR does not apply to those customers you can load all cookies on page load – Unless there are other local rules where cookie consent still applies.

However what you can do is improve the UX design to make it easier to click accept all cookies rather than reject all. Improving your data capture See below:

The Cookie Bar Popup
I normally set Enfold to essential cookies accepted on first page load only.
Button 1 – Accept All Cookies button – Accept all Cookies and dismiss the popup
Button 2 – Settings – Opens the modal

In the Modal:
They can turn cookies on and off in the modal.
Button 1 – Accept All Cookies button – Accept all Cookies and dismiss the popup
Button 2 – Do Not Accept – Reject all Cookies and Close window

This give the user the option to opt out but makes them more likely to click accept all to hide the message without going into the modal – Helping improve Analytics data while still being compliant.

I hope this helps!

Old thread but came up when I encountered a similar problem.
When using a host with a staging or dev environment like WpEngine, Siteground or Flywheel etc. or any server where a .htaccess password has been set.
Enfolds script merge function cannot verify the creation of the merged files and produces an error code 21 in the database merge fields.

The function should run correctly in live anyway
To resolve in staging environments – I assume for testing purposes – Remove the password temporarily and then turn script merging off and on again in the Enfold performance control panel and click save.
This will allow the process to verify the creation of the files and serve a merged script.
Live push – I would recommend disabling script merge and re-enabling it after going live because the process will need to run again in live anyway.
Hope this helps others.

• This reply was modified 3 years, 1 month ago by thinkjarvis. Reason: spelling mistake

This project was a conversion from an existing DIVI website.

Feel Positive Coaching ran by Fay Petcher is a holistic divorce and relationship coaching service. Fay is also an established Podcaster, Author and EFT Practitioner helping couples and individuals cope with narcissistic abuse, relationship trauma and infidelity.

The site was rebuilt in Enfold for ongoing support and performance features.
As part of the process the site was turned into a multi-page website from a one page design. Large padding and margins help give the site a modern – easy to scroll feel.
The logo and colour scheme were revised and entered into the Enfold theme control panel.

https://www.feelpositivecoaching.com/

The site scores 95/100 on mobiles in web vitals helping the site load quickly on all devices.

Performance stack:
Bespoke functions.php settings
WP-Optimize – Caching and HTML minification
EWWW WebP Conversion
Short Pixel thumbnail regenerator
Enfold Performance settings on
Bespoke .htaccess settings

Logo and Website designed by Think Jarvis Design and Marketing based in Swadlincote UK.

Hi Steve,

I was about to open a new thread about this.
When you set the header to a custom height since 4.8.6.4 it is no longer applying a fixed height on mobile devices below 989px wide.

I.e. I have a couple of sites with a 160px header and I can confirm they are now 160px on mobile devices instead of 90px on tablets and 80px on mobiles.

Add the following to Quick CSS to restore the usual heights on mobiles. This is a temporary fix.

@media only screen and (min-width: 768px) and (max-width: 989px) {
.responsive .logo a {
height:90px !important;
}
}

@media only screen and (max-width: 767px) {
.responsive .logo a {
height:80px !important;
}
}

• This reply was modified 3 years, 2 months ago by thinkjarvis.

@marcie73 @jay

There are multiple issues mentioned in your last posts and the solution will depend on your host and setup. It will be hard for the support team to advise further without looking at your actual setup in detail. Web vitals optimisation is bespoke and depends on any extra plugins and your server setup.

Without knowning your hosting setup it is difficult to advise on the best plugins to resolve the issue.

I tend to recommend Wp-Optimize as a free caching and html compression plugin. I let Enfold process the CSS and JS files from the performance panel. If you combine this with EWWW image compression plugin and Jetpack Boost. You have effectively added everything premium plugins can do without any extra costs.

Free critical CSS generator
Jetpack Boost includes a free critical CSS generator. This will remove the render blocking warning from Web Vitals but in most situations makes little difference to the performance scores. It can also cause some CLS issues because the CSS load order is altered by the inline critical CSS. So you will need to try it and see if it works for you without custom code in addition to the critical CSS.

Please see below to give you a better understanding of how web vitals works.
Most of the time a perfect score is impossible. This is because of the way elements load on the page.
Enfold is capable of a 90+ score. This is without critical CSS and without a CDN.

A CDN is only really needed if you have customers in multiple countries, or the actual server you have isnt very powerful so it uses the CDN to compensate for poor response times. Really, a CDN is designed to serve content from local servers to reduce server response times for global customers.

Critical CSS generators remove the render blocking warning and improve FCP and LCP in web vitals but can affect TBT scores negatively due to extra processing.

If you have added plugins that add extra front end elements then this will lower the performance score unless optimisation has been applied.

Hosting
The type of host you have will also depend on the plugins you need. If your host includes server side caching then you probably do not need a caching plugin at all. If your host has its own CDN like a dedicated wordpress host then this will also be cached serverside in most cases – So probably do not need a caching plugin.

Enfold on its own includes its own script merge function and some extra features that optimise wordpress itself (all in the performance panel) so the only things missing from the performance stack are Caching, Critical CSS and CDN.

If your server is a apache linux server you will need to add Gzip compression and cache control headers to the .htaccess file to remove these warnings. Most optimisation plugins can do this with one click setup.

If you want to reduce the size of your images you can use EWWW plugin to convert them to WebP. HOWEVER if your CDN uses Polish like Cloud Flares premium system it can be set to automatically convert and compress images. So depends on your setup and if your CDN includes image compression.

CDN and Font serving
A host like WPEngine automatically replaces URLs with the CDN URL once it is set up correctly. This includes fonts loaded via html/head.

If you added a third party CDN not provided by your web host – you will need to ensure that your DNS settings, any caching plugin and any CDN intergration plugin is configured properly to serve content via the CDN. So make sure you check the settings are correct.

Doing these last bits isn’t easy. You may find that removing the render blocking warning makes some of the other metrics worse.

I hope this helps!

• This reply was modified 3 years, 3 months ago by thinkjarvis.