I am currently using the WP Responsive Menu plugin on my WordPress site, and I’ve encountered an issue with the <meta name="viewport"> tag. The plugin seems to be modifying the viewport settings to the following:

<meta name="viewport" content="user-scalable=no, width=device-width, maximum-scale=1, minimum-scale=1">

However, I would like to allow users to zoom on mobile devices, and I need the viewport tag to look like this:

<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=3.0, user-scalable=yes">

Could you please guide me on how to modify or override the viewport settings applied by WP Responsive Menu? Any assistance or workaround to resolve this issue would be greatly appreciated.

Thank you in advance for your help.

Best regards

Is this feature available on Pro?

ShortPixel CDN does not store images until a device accesses them. So there is no guarantee that origin web server image won’t be loaded for a user. This behavior is problematic if the origin server image is large and uncompressed and because of the latency cost to request from the origin server.

I have a few questions based on the above context.

• Why does optimization of image take so long on first load? WP Compress claims to load as fast as 7 ms, so how is ShortPixel running compression slower than them on first load?
• How does optimization of image work? Is ShortPixel processing image for every device with even 1-px difference or is it using breakpoints?
• Why not srcset? What is the benefit of ShortPixel CDN when the user can put srcset in the HTML, then have a CDN store all srcset images and load that way?
• What is optimal 307 Fallback Strategy? When the image is requested from origin web server, it must be optimized (resized, compressed) still. But then doing that will make ShortPixel attempt to resize and compress an already resized and compressed image.
  
  So, alternative to above is to use srcset with breakpoints, so when user requests image, it requests correct size?
  
  This strategy still requires origin web server to resize and compress all of those breakpoints for first load. So, wen the origin server is doing that, why not use a CDN that stores those images and loads them from client via srcset instead of calculating “on-the-fly”?
  
  What am I missing here?

Adaptive Images is theorized to read screen size of user, then serve image accordingly. So how does this plugin implement that?

Some background information:

• https://www.ads-software.com/support/topic/plugin-did-not-work-it-did-not-cache-any-image/ indicates that the plugin’s resizing and compression runs from origin server.
• https://www.ads-software.com/support/topic/adaptive-images-dont-appear-to-be-rendering/ indicates that the detection of user screen size happens from origin server.
• https://www.php.net/manual/en/book.image.php requirement indicates origin server uses get_image_size to get image size from server-side PHP execution rather than frontend JS execution. So, request in order of user -> origin web server -> php -> html -> user. This order is why plugin “doesn’t work” on CDN, because that would be user -> cdn -> html -> user, but html doesn’t call to origin web server to run php.
• https://www.ads-software.com/support/topic/taking-care-of-all-the-thumbnail-generation/ indicates that images are “only created if and when they are requested by devices with relevant screen sizes and based on the breakpoints set in its settings”. So, images only resized if loaded by user and then it creates images at the size of given breakpoint and stores that in the cache. So, images might end up taking time on new requests.

So, if you are using breakpoints, why not

1. When image is uploaded, generate all breakpoint image variations.
2. Change all HTML to use srcset, which will also serve “as small, but not too small, images based on each device’s dimensions” with its media query.

Plugin doesn’t work with CDN because plugin doesn’t change HTML to use breakpoint images. So, on first page load, CDN -> origin web server -> html (requests original image) -> cdn (stores original image) -> user. Then, user -> cdn -> user (always receives cdn-original-image).

Or alternatively, CDN receives an “adaptive image” once, then never changes it to avoid origin server.

So how does the plugin work and why not use srcset instead?

I have a WordPress version 5.8.3, with a plugin of a regular editor (Gutenberg does not fit my tasks)

I need to implement a page with photos and videos – in an adaptive version for different devices (photos with full-screen opening)
https://test.contactimprovisation.ru/foto-video / is an example of how to do it (implemented on the constructor)

This is how I did it with a simple method of adding photos and videos
https://test2.contactimprovisation.ru/foto-i-video/

And it doesn’t adapt to the mobile version.

Which plugins do you recommend ?
Or is it easier to make a code ?
For photos – you need something very simple (a small plugin) – because there will be few photos

There will be more videos and on different platforms:
YouTube, vimeo, Facebook and other less popular

– The team developing the ”VW Security Guard template” is just FANTASTIC!!
– Support is acting very fast and effectively.
– Request to adapt the template to my own needs has been resolved under 6 hours!
– Clear and fast communication!

Will for sure do business again with them, they really deserve a look!!

Many thanks Shivani Akojwar, Hasan Diwanji from vwthemes.com
Well done guys, keep it up like this!

Best regards,

sacha
sAco2web.ch