Jose Mortellaro

<p>It removes cookies from the requests to static resources for modern browsers.</p>
<p>When the browser requests a static resource such as an image, a stylesheet, or a script, it sends to the server all the cookies, and it does it at every request.<br />
If your page requests 10 scripts, then it sends 10 times the cookies.<br />
As you have probably heard, a way to solve this issue is to serve the static resources from a cookies-free subdomain.<br />
The cookies-free subdomain is a possible solution, but sometimes you have no wish to create a subdomain only for the static assets and give instructions to WordPress for fetching them from the subdomain.</p>
<p>Moreover, why don’t we solve this issue directly at the root? Is the browser that sends cookies to the server, so let’s address this issue with the browser.<br />
This is exactly what Remove Cookies From Static Resources does. It instructs the browser to don’t send its cookies when it requests static resources.<br />
However, this solution will work only with the modern browsers that support the crossorigin attribute.<br />
The plugin simply adds crossorigin=”anonymous” to all the requested scripts, links, and images. Nothing else.<br />
This plugin will not work for old browsers. It will also not work for all those resources that are added with JavaScript, or CSS.</p>
<p>This plugin has no settings. No additional HTTP requests, no additional database queries. It consumes practically zero.</p>
<p>You should see an improvement in performance if yor website requests many static resources sending big data through the cookies.<br />
In all other cases you don’t need this plugin, as you would not need to serve static resources from a cookies-free domain.<br />
Removing cookies from static resources is not always the performance saver that some people think. This is totally not true in many cases.<br />
In most cases the cookies aren’t the cause of bad peformance, but the resources itselves. In those cases, it would be more effective totally removing the resources that you don’t need everywhere with <a href="https://wordpress.org/plugins/freesoul-deactivate-plugins/" rel="ugc">Freesoul Deactivate Plugins</a>.</p>
<p>Of course, removing cookies from static resources improves also the privacy of your visitors.</p>
<p>As a side note, removing cookies form static resources with this plugin will have no impact on the score given by some speed meters.<br />
The speed meters only check if the static resources are requested to free-cookies domains, but they don’t check the crossorigin paramenter.</p>
<h3><a href="https://josemortellaro.com/remove-cookies-from-static-resources/" rel="nofollow ugc">How to remove cookies from static resources</a></h3>
<ul>
<li>Install Remove Cookies From Static Resources</li>
<li>Done!</li>
</ul>
<h3>How to understand if I really need to remove cookies from static resources</h3>
<ul>
<li>Go to your website</li>
<li>Right-click => Ispect => Console => write document.cookie.length and press enter</li>
<li>If you see a number higher than 5000 you probably need this plugin to save bandwidth due to big data transfers through the cookies. For lower numbers you will probably not need this plugin.</li>
</ul>
<h3>Does removing cookies from static resources always improve the performance?</h3>
<p>Absolutely not! It improves the performance only if yor website requests many HTTP requests due to static resources and it writes many data to the browser through the cookies.</p>
<h3>Limits</h3>
<ul>
<li>This plugin doesn’t work for old browsers that don’t support the crossorigin attribute</li>
<li>This plugin doesn’t work for all those resources that are added with JavaScript or CSS, and probably it will never work in those cases, neither with future versions of the plugin.</li>
</ul>
<h3>Backend Speed Optimization</h3>
<p>Need a faster WordPress admin? I specialize in backend performance optimization.<br />
Read <a href="https://josemortellaro.com/backend-speed-optimization/" rel="nofollow ugc">Backend Speed Optimization Service</a> for more information.</p>


Remove Cookies From Static Resources

It removes cookies from the requests to static resources for the modern browsers.

<p>Specific Content For Mobile allows you to create pages and posts content designed for mobile devices.</p>
<p>This plugin <strong>DOES NOT</strong> redirect content from the desktop website: it creates brand new mobile-specific content.</p>
<p>It’s perfect if in some pages you need different content for the mobile version.</p>
<p>The best way to have a mobile version is always a fully responsive design, but in some cases you may need <strong>specific content for the mobile version</strong>.</p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/-vc3zBI9Prw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h3>How to add or remove specific content for the mobile version:</h3>
<ul>
<li>Click on Pages in the main admin menu</li>
<li>Go with your mouse on the page you want to modify for the mobile version and click on the action link “Create mobile version”, or click on the icon “+” you see in the devices column</li>
<li>Modify your page as you want to see it on mobile</li>
<li>Save your page mobile version</li>
</ul>
<p>If you want to create a mobile version for your blog posts, do as explained above, but going to the list of Posts.</p>
<p>On mobile devices, the plugin will load the mobile version you have created for that page or post.</p>
<p>If you create the mobile version for a page reachable at https://your-domain.com/page-example/, and you are logged-in, you will see also https://your-domain.com/page-example-mobile/.<br />
But logged-out users will not see it, and the only URL that exists for the public is https://your-domain.com/page-example/.</p>
<p>The page reachable at https://your-domain.com/page-example/ will show the desktop content on desktop devices, and the mobile content on mobile devices The URL is always the same.</p>
<p>You have <strong>no redirections</strong>, and the plugin just replaces the desktop content with the related mobile version.</p>
<p>For more details read the <a href="https://specific-content-for-mobile.com/documentation/" rel="nofollow ugc">Documentation</a>.</p>
<h3>Requirements</h3>
<p>If you have a server cache plugin, be sure to set a different server cache handling for mobile devices, in another case the mobile version of your pages could also be served on desktop devices.<br />
E.g. <a href="https://wordpress.org/plugins/w3-total-cache/" rel="ugc">W3 Total Cache</a>, <a href="https://wordpress.org/plugins/wp-fastest-cache/" rel="ugc">WP Fastest Cache</a>, and <a href="https://wordpress.org/plugins/powered-cache/" rel="ugc">Powered Cache</a> are caching plugins that can handle the mobile cache.<br />
Be careful if you are using <a href="https://wordpress.org/plugins/w3-total-cache/" rel="ugc">W3 Total Cache</a> or whatever other caching plugin that gives you the possibility to manage the mobile version, DO NOT set up any redirection for mobile devices.<br />
If you have issues with the mobile and desktop versions with W3 Total Cache, read <a href="https://wordpress.org/support/topic/mobile-version-showing-in-desktop-view-w3-total-cache-plugin/#post-17279915" rel="ugc">Mobile version showing in desktop view – W3 Total Cache Plugin</a><br />
Specific Content For Mobile <strong>DOES NOT</strong> redirect the mobile users. <strong>The URL of a page visited on mobile is exactly the same as the desktop URL.</strong></p>
<h3>Differences with AMP plugins</h3>
<p>Specific Content For Mobile has nothing to do with AMP pages. It gives you the possibility to show specific content for mobile, but without any redirection, and without generating any AMP markup.<br />
If you want to serve AMP pages, Specific Content For Mobile is not for you. In that case, you may be interested in a plugin like <a href="https://wordpress.org/plugins/amp/" rel="ugc">AMP</a>, or <a href="https://wordpress.org/plugins/accelerated-mobile-pages/" rel="ugc">AMP For WP</a>.<br />
You consider Specific Content For Mobile like an alternative to AMP plugins.</p>
<h3>Limitations of the free version</h3>
<p>The free version supports only the mobile version of pages and posts, no custom post types, no archives, no terms.</p>
<h4>I need advanced functionality to be integrated with this plugin.</h4>
<p>If you need custom functionality, I offer a development service for WordPress plugin integrations and advanced feature extensions.<br />
Learn more about <a href="https://josemortellaro.com/advanced-functionality-for-wordpress/" rel="nofollow ugc">advanced functionality for WordPress</a>.</p>
<h3>Additional information</h3>
<p>As a default, WordPress doesn’t output the blog page content before the posts loop.<br />
Some themes do it. In this case, the blog page content output before the loop is handled by the theme templates.<br />
The plugin will check if the theme declares support for the blog page mobile version, if not so the blog page mobile version may take the original desktop content.</p>
<p>As a default Specific Content For Mobile synchronizes the post metadata. This means that when you save a post or page, if they have a mobile version, the same metadata will be saved in the mobile version.<br />
When you save a mobile version, the mobile version metadata will be saved also in the desktop version.<br />
If you want to change this behavior, go to Specific Content For Mobile settings and choose “Allow mobile versions having their own metadata”.</p>
<p>For the most popular SEO plugins, you can choose the metadata synchronization specifically for that plugin.</p>
<h3><a href="https://specific-content-for-mobile.com/documentation/" rel="nofollow ugc">PRO Version</a></h3>
<h4>The <a href="https://specific-content-for-mobile.com/documentation/" rel="nofollow ugc">PRO version</a> also allows you to:</h4>
<ul>
<li>Have a mobile version of all the queriable post types are supported</li>
<li>Load a different theme specifically on mobile devices</li>
<li>Unload specific plugins only on mobile devices</li>
<li>Decide if tablets should be considered as mobile devices or not so</li>
<li>Have a different navigation on mobile</li>
<li>Write specific content depending on the device</li>
<li>Have access to the premium support</li>
</ul>
<h3>For developers</h3>
<p><strong>Template for mobile</strong></p>
<p>If you need to use a different template file on mobile, copy the template file of your theme and put it in one of these folders:</p>
<p>wp-content/scfm/</p>
<p>wp-content/themes/theme-name/scfm</p>
<p>For example, if your theme is “theme-name” and you want to load a different page.php on mobile, it will be something that looks like:</p>
<p>wp-content/scfm/page.PHP</p>
<p>or</p>
<p>wp-content/themes/theme-name/page.php</p>
<p>In the case of mobile devices, Specific Content For Mobile will look for the custom template file first in wp-content/themes/theme-name/scfm and if it doesn’t find it in wp-content/scfm.</p>
<p><strong>Integration with other plugins</strong></p>
<p>If you add an option for the metadata synchronization of an external plugin, you can use the filter “eos_scfm_meta_integration_array”.</p>
<p>Here an example:</p>
<pre><code>add_filter( 'eos_scfm_meta_integration_array','my_custom_scfm_meta_integration',20,2 );
//It adds an option to synchronize your plugin meta data.
function my_custom_scfm_meta_integration( $arr,$options ){
    $slug = 'my_custom_meta';
    $arr[$slug] = array(
        'is_active' => defined( 'WPSEO_FILE' ),
        'args' => array(
            'title' => __( 'My custom meta synchronization','my-textdomain' ),
            'type' => 'select',
            'value' => isset( $options[$slug] ) ? esc_attr( $options[$slug] ) : 'synchronized',
            'options' => array(
                'synchronized' => __( 'Synchronize desktop and mobile metadata','my-textdomain' ),
                'separated' => __( 'Allow mobile versions having their own metadata','my-textdomain' )
            ),
        ),
        'prefix' => array( '_my_plugin' ),
        'default' => 'synchronized'
    );
    return $arr;
}
</code></pre>
<p>Then you will see your custom option “My custom meta synchronization” in the main settings page.</p>
<p><strong>Helper functions</strong></p>
<p>In your theme, you can use the following functions to give full support to the mobile version content:</p>
<pre><code>eos_scfm_related_desktop_id( $post_id );
</code></pre>
<p>given the post ID, it will get the post ID of the related desktop version.</p>
<pre><code>eos_scfm_related_mobile_id( $post_id );
</code></pre>
<p>given the post ID, it will get the post ID of the related mobile version.</p>
<p><strong>Theme support</strong></p>
<p>To add the theme support to the blog content, you can add this line in your theme support action hook:</p>
<pre><code>add_theme_support('specific_content_form_mobile',array( 'posts_page' => true ) );
</code></pre>
<h3>Help</h3>
<p>If something doesn’t work on the free version, open a thread on the <a href="https://wordpress.org/support/plugin/specific-content-for-mobile/" rel="ugc">support forum</a><br />
If you are a PRO user, and you have issues, don’t hesitate to open a ticket on the <a href="https://specific-content-for-mobile.com/support/" rel="nofollow ugc">premium support</a></p>


Specific Content For Mobile – Customize the mobile version without redirections

Specific Content For Mobile allows you to create pages and posts content designed for mobile devices.

Remove Cookies From Static Resources vs Specific Content For Mobile – Customize the mobile version without redirections