lhotc

Resolved

Hi and thanks. I missed that setting, so this works now.

(tried to disable other plug-ins as well before)

thanks a lot again

jan

I take it back. it was our caching.

same problem here without the slider.

Hi
I found that using sg optimizer lazy loading, in Chrome you do get CLS, as Chrome for some reason allocates a square as the space for the image, independantly of the actual aspect ration.
You can check by loading your site, but not scrolling. Then right click in your side and select inspect. In the Dev Tools window scroll down to an image and look in the attributes what dimensions Chrome thinks the image is.
If it is different then your image size, it would mean that when loading the actual image (when scrolling) the space allocated would change. Especially on slow internet connections or when scrolling really quickly this will cause CLS.
Cheers
Jan

I have the same issue, but the image has width and height defined.
i.e. width=804, heigth= 1020.
Chrome shows this before loading as 804x804px, then load and the image is actually 804x1020px. This results in a high Cumulative Layout Shift score especially on slow internet connections and when somebody is scrolling down quickly.
When I switch lazy loading off in sg-optimizer, this behaviour goes away and the image stays as 804px x 1020px the whole time (even when not in view and way down the website). This happens for all images btw.
I think this is an issue with SG-Optimizer, and can only be fixed there.
Thanks

Yep, as per John’s comment, it works again.
Thanks

yep, same for me…
I can see the following stacktrace:

Uncaught TypeError: blocks is undefined
    FindMyBlocks https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:192696
    renderWithHooks https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:24450
    updateFunctionComponent https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:26629
    beginWork https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:28154
    callCallback https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9843
    invokeGuardedCallbackDev https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9892
    invokeGuardedCallback https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9945
    beginWork$1 https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:32706
    performUnitOfWork https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:31673
    workLoopSync https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:31646
    performSyncWorkOnRoot https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:31264
    flushSyncCallbackQueueImpl https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20784
    unstable_runWithPriority https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9091
    runWithPriority$1 https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20730
    flushSyncCallbackQueueImpl https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20779
    flushSyncCallbackQueue https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20767
    scheduleUpdateOnFiber https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:30707
    dispatchAction https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:25287
    useBlocks https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:34550
find-my-blocks.js:192696:1
The above error occurred in the <FindMyBlocks> component:
    in FindMyBlocks

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries. find-my-blocks.js:29062:17
Uncaught (in promise) TypeError: blocks is undefined
    FindMyBlocks https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:192696
    renderWithHooks https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:24450
    updateFunctionComponent https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:26629
    beginWork https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:28154
    callCallback https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9843
    invokeGuardedCallbackDev https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9892
    invokeGuardedCallback https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9945
    beginWork$1 https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:32706
    performUnitOfWork https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:31673
    workLoopSync https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:31646
    performSyncWorkOnRoot https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:31264
    flushSyncCallbackQueueImpl https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20784
    unstable_runWithPriority https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:9091
    runWithPriority$1 https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20730
    flushSyncCallbackQueueImpl https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20779
    flushSyncCallbackQueue https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:20767
    scheduleUpdateOnFiber https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:30707
    dispatchAction https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:25287
    useBlocks https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707:34550
find-my-blocks.js:192696:1
Source map error: Error: request failed with status 404
Resource URL: https://www.littlehouseonthecorner.com/wp-content/plugins/find-my-blocks/find-my-blocks.js?ver=1616438707
Source Map URL: /find-my-blocks.js.map

Hi Daan,
Happy new year.

sorry I wasn’t clear.

Our ads publisher uses the UA stats for their calculations and we need to get used to GA4 and see what it can do. And as far as I read it is a viable scenario to run them in parallel for a transition period at least (apparently this can be 2-3 years).

Of course the cookies are not set, but then they are the only change that I could find from CAOS setup to mine. And mine works with connected site tags, but the version with cookies does not. Does that make sense?

Cheers
Jan

Hi ya,

in class Install_5_3_4 you are doing this:

public function install() {
$new_handles = array(
‘jquery-core’,
‘jquery-migrate’,
);

I just wanted to double check if this means that you need jquery-migrate. I haven’t looked into the code, just popping the question was easier. (I now think this is for the exclude list, isn’t it?).
If you do not depend on it, I will unload it using another plugin.

cheers
jan

I agree with this. Adding additional tags to the script would be very useful indeed.

Hi,
I switched on the the “full page cache” in SG-Optimzer and a few hours later my worker reqeust limit of 100k requests was reached. It does not look like an alternative to APO (at least not for me)
Jan

@hristo-sg : so the difference between APO and SG-Optimizer will be the edge cache from CF?
Thanks
Jan

Hi,
I took the screenshots and set the setting back to relative path to show you the error as well, but it is no longer duplicating the path. I assume some caching problem? (I did not empty the cloudflare cache, just the dynamic cache of the website, shame on me). So I basically cannot reproduce it now, sorry.

Similar issue to cyberpunks627: when using relative paths, part of the path is duplicated: …/wp-content/uploads/omgf/hyd-google-fonts/wp-content/uploads/omgf/hyd-google-fonts/font.woff2
when not using relative path it works.