You can try something like this below. There are some caveats using this, but for some situations it is worth using.
@media screen and (min-resolution: 120dpi) { body {transform: scale(0.8);transform-origin:top left;width: 125%;height: 125%;} }
Comment /*body....*/ An example of a scale may be easier to understand even worse, i.e. because scaling should be done based on the right right edge of css transform-origin. Then everything can be improved, especially in Chrome.
if you use width: 125% , your RWD css should react differently to resizing the browser based on what you expected when the screen ratio was 100%. And you can reasonably accept this - this is RWD, and the difference is 25%. But some people may want to adapt their css as follows:
@media screen and (min-width: 1000px)
You also need to configure:
@media screen and (min-width: 800px)
probably not 1250px, but 800px like me.
Edge, Chrome, FF are doing very well. IE 11 did the worst, but not hopelessly.
In FF (not edge, chrome) there are some problems when expanding selection fields - choosing a css solution. Some borders may be visible; some disappearing on FF (possibly not edge, chrome)
There may be some problems not mentioned here, for example, when you use a carousel, like owlcarousel on your page.
However, I think it is more likely to save more time, as this example has not been tested too much.
You need to use precise scaling, for example 0.8 for a 125% screen, so that your images are displayed as sharply as possible.
I noticed that when switching to different dpi resolutions using ctrl + / i in a desktop browser and, of course, using multi-touch gestures in mobile browsers, the browser also changes dpi, so any solution using @media min / max- resolution, may not work as expected. What you need in css is to read the resolution of the system, not the browser. However, as I see it, this resolution change does not occur, as when someone resizes the browser manually or rotates the mobile device.
Thanks to Tatsuyuki Ishi for fixing some of the errors in my answer.