Forum Replies Created
-
AuthorPosts
-
September 17, 2021 at 12:41 am in reply to: Pagespeed insight complains about non supported CSS properties #33897
Bernhard
ParticipantHi Elvin,
I’m wondering if it’s necessary to investigate further. The PSI index is >90 and no CLS caused by this issue. I checked with different browser and everything seems ok.I looked also into the PSI results for desktop and there it says also
Unsupported CSS Property: color
so this could become a never ending story. On my site, the flex shrink message seems to be an all overlay lists with zoom on hover and more than one card. Maybe the new WPSP version will solve the problem?About the 3 lists on mobile, probably I will make a version with only one card for mobile.
Thank you 🙂
September 16, 2021 at 12:41 am in reply to: Pagespeed insight complains about non supported CSS properties #33868Bernhard
ParticipantNow a third list also gives the error.
September 15, 2021 at 7:26 am in reply to: Pagespeed insight complains about non supported CSS properties #33846Bernhard
ParticipantOK, with this CSS the padding-bottom, flex-grow, padding-left, padding-right, padding-top disappear.
The flex-shrink message persists and it is only on two lists, which are set to show 3 cards in 3 columns on all devices. I have other lists on the page with identical settings which show only 1 card in 1 column on mobile and there the error is not present.
The only way to make the Unsupported CSS Property: flex-shrink error disappear is diabling image zoom on hover.
When I hover over the description in PSI screenshot (src=…) I see
div.wp-show-posts-inner > div.wp-show-poss-image > a > img.center
September 15, 2021 at 12:48 am in reply to: Pagespeed insight complains about non supported CSS properties #33828Bernhard
ParticipantDo you mean “combine CSS”? I did but it makes no difference.
The problem is also that the error appears randomly. When I disabled image zoom on hover, probably it disappeared. At least, when I tested more times the error did not reappear.For the GB buttons, 3 lines of css code were enough to solve the problem, is there no such solution for the error messages here? In first line non supported CSS property flex-shrink, and then less often padding-bottom, flex-grow, padding-left, padding-right, padding-top
September 14, 2021 at 11:16 pm in reply to: Pagespeed insight complains about non supported CSS properties #33825Bernhard
ParticipantThese are the image settings of the overlay cards screenshot
September 14, 2021 at 11:04 pm in reply to: Pagespeed insight complains about non supported CSS properties #33823Bernhard
ParticipantHi Elvin,
these are my CSS settings in WP Rocket screenshotI have the following CSS for WPSP:
.entry-content .wp-show-posts-entry-title { min-height: unset; } .entry-content .wp-show-posts:not(.wp-show-posts-columns) .wp-show-posts-single:not(:last-child) { margin-bottom: 0.5em; } @media(max-width:768px){ section#wpsp-37158 { margin-bottom: 0.5em; } }
September 14, 2021 at 1:37 pm in reply to: Pagespeed insight complains about non supported CSS properties #33794Bernhard
ParticipantHello,
I checked today again and the problem of the non composited animations is still there. So it’s not a cache problem. Is there a way to solve it?September 9, 2021 at 10:00 pm in reply to: Pagespeed insight complains about non supported CSS properties #33647Bernhard
ParticipantOK, the GB Button problem has been solved.
I rechecked and found, that the problem still appears randomly with WPSP, even since the css files are excluded. Checking different posts and pages, it reappears sometimes. Checking the same page more times, it may happen that the first view is ok and the problem appears with the second view or viceversa. Screenshot
September 8, 2021 at 1:16 am in reply to: Pagespeed insight complains about non supported CSS properties #33588Bernhard
ParticipantOk, for now the problem with WPSP is solved excluding the 4 css files.
Please note that the problem is only with the overlay cards. Base and polaroid cards have not this problem. I know that there will be a major release of WPSP. Probably you can check what happens.
Now I have still the same problem with Generateblocks buttons.
September 7, 2021 at 1:50 am in reply to: Pagespeed insight complains about non supported CSS properties #33548Bernhard
ParticipantHi Elvin,
it disappears when WP Rocket is disabled.Bernhard
ParticipantPerfect, thank you 🙂
Bernhard
ParticipantHI Elvin,
I mean list IDs.Bernhard
ParticipantHi Tom,
I have now the following code repeated for every involved post/page id:add_action( 'wpsp_after_content', function( $settings ) { $custom_field = get_post_meta( get_the_ID(), 'wpsp_title2', true ); if ( $custom_field && 123 === $settings['list_id'] ) { echo '<h2>'; echo $custom_field; echo '</h2>'; } } );
Is it possible to put all the Id’s in a unique array like ( 123, 124, 125 ) ?
Bernhard
ParticipantIt works, thank you 🙂
Bernhard
ParticipantPerfect, thank you 🙂
-
AuthorPosts