Hey GWS,

Thank you for the inquiry.

We are not really sure why the items are not sorting correctly, but we do know that there’s a known quirk with the masonry or isotope script where sorting may fail at times, often due to differences in content or image sizes between items.

Please try this script in the functions.php file and let us know the result:

add_action('wp_footer', function () {
    ?>
    <script>
    document.addEventListener('DOMContentLoaded', function () {
        const masonryContainer = document.querySelector('.av-masonry-container');
        if (!masonryContainer) return;

        const masonryItems = Array.from(masonryContainer.querySelectorAll('.av-masonry-entry'));

        const masonryWithDates = masonryItems.map(item => {
            const dateElement = item.querySelector('.av-masonry-date');
            const dateText = dateElement ? dateElement.textContent.trim() : '';
            const parsedDate = new Date(dateText);
            return { element: item, date: parsedDate };
        });

        masonryWithDates.sort((a, b) => b.date - a.date);

        masonryWithDates.forEach(({ element }) => {
            masonryContainer.appendChild(element);
        });
    });
    </script>
    <?php
}, 9999);

Best regards,
Ismael

Hey Brugmedia,

Thank you for the inquiry.

The “cloudy sky” background seems to be displaying correctly on our end. Would you mind providing a screenshot of the changes you’d like to make? You can upload and share it using platforms such as Savvyify, ImgBB, PostImages, or Dropbox.

Best regards,
Ismael

Hi,

Glad to know that switching to another image editor or image extension resolved the issue. Please feel free to open a new thread if you have any further questions.

Have a nice day.

Best regards,
Ismael

Hi,

Thanks for the update. So you want the images next to each other on mobile?

Best regards,
Rikard

Hey condonp,

Thank you for the inquiry.

Adding this css code should center-align the images in the footer widgets on smaller screens.

@media only screen and (max-width: 768px) {

  /* Add your Mobile Styles here */
  #footer .widget.widget_text {
    margin: 0 auto;
  }
}

Please make sure toggle or temporarily disable the Enfold > Performance > File Compression settings, then purge the cache before checking the page.

Best regards,
Ismael

Hi,

The configuration looks typical for WordPress installations — almost the same as our local installation. What configuration did you add to your .htaccess file?

Another thing you can try is to switch the default image editor from WP_Image_Editor_Imagick to WP_Image_Editor_GD to see if that helps.

— https://developer.wordpress.org/reference/hooks/wp_image_editors/

We tried uploading six files to the media library, around 6MB, and it took about 10 seconds or less. It’s not particularly fast, but not terribly slow either. We also noticed that you’re using a custom media library plugin (WP Media Folder), which could be contributing to the slowdown. Have you tried disabling this plugin to see if it makes a difference?

Best regards,
Ismael

Hi,

Thank you for the update.

You can add this css code to adjust the width of the featured images in mobile view, make sure they don’t overflow outside the screen.

@media only screen and (max-width: 989px) {

  /* Add your Mobile Styles here */
  #top.single-post .fullsize .template-blog .big-preview img {
    width: 100%;
    min-height: auto;
    object-fit: contain;
  }
}

Result:

Best regards,
Ismael

Hi,

We are not encountering this issue on our end, and there have been no similar reports from other users, so this is probably related to your server configuration or specifications. Where is the site hosted, and what are the server specs?

If you have access to your PHP configuration or php.ini, try to add the following options:

max_execution_time = 300
memory_limit = 512M
upload_max_filesize = 20M

You can also add it in the .htaccess file in the root directory of your WordPress installation.

php_value max_execution_time 300
php_value memory_limit 512M
php_value upload_max_filesize 20M

Another thing you could try is disabling the thumbnails generated by the theme using this filter in the functions.php file:

add_action('init', 'ava_remove_enfold_image_thumbnails');
function ava_remove_enfold_image_thumbnails() {
  remove_image_size('square');
  remove_image_size('featured');
  remove_image_size('featured_large');
  remove_image_size('portfolio');
  remove_image_size('portfolio_small');
  remove_image_size('gallery');
  remove_image_size('magazine');
  remove_image_size('masonry');
  remove_image_size('entry_without_sidebar');
  remove_image_size('entry_with_sidebar');
  remove_image_size('shop_thumbnail');
  remove_image_size('shop_catalog');
  remove_image_size('shop_single'); 
  remove_image_size('shop_gallery_thumbnail');
}
add_filter( 'intermediate_image_sizes_advanced', 'ava_intermediate_image_sizes_advanced_mod' );
function ava_intermediate_image_sizes_advanced_mod( $sizes ) {
 unset( $sizes['large']);
 unset( $sizes['medium_large']);
 return $sizes;
}

We recommend reaching out to your hosting provider for additional assistance.

Best regards,
Ismael

Hi,

It’s actually good to disable lazy loading for elements that affect LCP because lazy loading can delay their appearance. In this case, it’s already handled correctly, so there’s nothing you need to do for this part.

For the fetchpriority issue, if you’re using Image layers in the Layer Slider, go to Layer Settings > Attributes > Custom Attributes tab of the layer, then add fetchpriority as the attribute and set its value to high. The following article should explain what this attribute does.

— https://addyosmani.com/blog/fetch-priority/

Best regards,
Ismael

Hey Valerie,

Thank you for the inquiry.

Where can check the issue? Please provide a screenshot using platforms like Savvyify, ImgBB, PostImages or Dropbox, then create a test page so we can inspect the elements.

Best regards,
Ismael

Hi,
When I check your test page the “opening frame” is relly the background image so use this css to hide:

#top.page-id-11644 #av_section_1 {
        background-image: none;
}

note the page ID in the css, remove or adjust for your working page.
Then leave Ismael’s script to stop the loop and add this script to end on the last frame/second, your video is 29s so the script ends on 28s. Adjust for future videos and adjust the page ID.
Add this to your child theme functions.php:

function pause_video_on_last_sec() { ?>
  <script>
if (document.body.classList.contains('page-id-11644')) {
    var x = document.getElementsByClassName("avia_video");
    var i;
    for (i = 0; i < x.length; i++) {
        x[i].addEventListener("timeupdate", function(){
            if(this.currentTime >= 28) {
                this.pause();
            }
        });
    }
}
</script>
  <?php
}
add_action( 'wp_footer', 'pause_video_on_last_sec', 99 );

Best regards,
Mike

Hi,
This looks like a caching issue, when logged in the homepage hero image shows, and the theme css is served, when logged out the cache css is served: /wp-content/cache/wpfc-minified/q6rb0fb4/hwyv4.css without the css for the hero image.
Your test page is not cached by the plugin and serves the theme css when logged out, thus the image shows.
Your cache plugin is probably set to not show a cache to mobile devices, because the theme css is also showing, along with the image.

Best regards,
Mike

Hi,

Thank you for the update.

The featured image seems to be displaying correctly on our end. Would you mind explaining the issue further? If possible, please open another thread so we can close this old one.

Best regards,
Ismael

Hi,

Thank you for the update.

The page speed reports clearly point to the Revolution Slider as the cause of the LCP issue, so it’s definitely the reason for the decreased score. On the second site, you’ll notice there is no LCP issue because the Revolution Slider only contains static images, without moving parts or animations, unlike the first site, which uses complex slides and effects.

This is the LCP report — note the element sr7-module#SR7_31_1.

LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loadingLCP
lazy load not applied
fetchpriority=high should be applied
Request is discoverable in initial document
sr7-module#SR7_31_1 > sr7-content > sr7-slide#SR7_31_1-130 > sr7-img#SR7_31_1-130-23

Fixing this LCP issue should significantly increase the overall score. We recommend reaching out to the plugin developers for additional information about the issue.

Best regards,
Ismael