Search Results for 'mobile theme'

Additionally: We do not want to use the tagDiv Mobile Theme.

I have deactivated all plugins except the four tagDiv plugins, namely tagDiv Cloud Library, tagDiv Composer, tagDiv Mobile Theme, and tagDiv Opt-In Builder (see screenshot: [https://prnt.sc/WBSe10lJObBx](https://prnt.sc/WBSe10lJObBx)).

Despite this, the homepage still takes nearly 60 seconds to load.

From my observations, the slowdown only occurs when an admin is logged into the WordPress dashboard and opens the homepage in the same browser. The issue is consistent across browsers, as long as the admin session and the homepage are accessed within the same browser. Once the admin logs out, the homepage loads very quickly.

Similarly, the website loads fast on any browser where no admin is logged in.

There is also a related issue during publishing. When attempting to publish a post, the process is often slow, with the loading indicator continuing for an extended period, and sometimes ending in an error message. However, after refreshing the page, the post appears to have been successfully published.

You likely experienced the same issue some time back on this thread because you were logged into the WordPress admin and accessed the homepage using the same browser session.

This situation has significantly affected our workflow.

Please investigate this and advise on a solution.

Thank you for your continued support.

Hello, Calin. Thank you for replying. I’m not using image ads, I’m using non-Google banner ads that are not images. I pasted the ad code into Custom ad 2 in the Theme panel. Then I dragged the box ad to the mobile header. Then I chose Custom ad 2 in TagDiv composer. However, when I click the other viewports, the Custom ad 2 code shows in all 4 viewports. I only want the mobile ad to show on mobile.

https://prnt.sc/C6uyCYwPpGbl

I have designed the template as needed for me. For me I need “LC – Single Template” as my mobile view and “Single Post Template – Free News” as my computer view. How can I set it. I checked for the option by copying the “LC – Single Template” and making to mobile version but still when I give the mobile template option again the issue is raising for the header and footer as its not coming as intended.

https://prnt.sc/5lCrMMCukAqM

At the same time I only have one header and one footer. The only issue is that when clicking the mobile view, I am getting the below header and footer which is not present while editing the mobile view via tag div

Header and footer which I dont want and which comes when I click mobile version of the theme I want:

https://prnt.sc/bmwv-EnUe2yI
https://prnt.sc/thtJ3oi1fUbl

This is how front end shows me for the same mobile version tagdiv composor:

https://prnt.sc/XmKcb7mcrvEm
https://prnt.sc/x21NvOxFkM-f

I need exactly like this in mobile version without the black header and footer

Perfect!!

Thanks for your recommendation. I’ll continue as I am now; I won’t activate the mobile theme plugins. The theme looks great as it is.

Regarding the plans, is there a way to preview the post content or enable “Excerpt” on the post? Something like this screenshots from Entrepreneur.com

https://prnt.sc/EfvJxtCrxr51
https://prnt.sc/WOxHf_4aF9Rh

Thanks!!

Hi, thank you for the clarification.

Yes — I’m referring to the Single Post Mobile Template created in tagDiv Composer, not the old Mobile Theme plugin.

If I choose a smaller featured image size in the mobile template (for example 696px or 1068px), will the theme still generate the full srcset, including the larger versions (1200px+, 1600px, 1920px), as long as the originally uploaded image is large enough?

This is important because Google Discover requires the mobile HTML to expose an image of at least 1200px in the srcset, not only in the desktop template.

So my question is:

Does selecting a smaller display size in the mobile template limit the largest image included in the srcset, or will the theme always include the full-size variants if they exist?

Thanks again for your help.

https://prnt.sc/zu33gXOKP196

I have checked in another browser also but its the same and also its not showing the responsive theme. Already the mobile theme app is deactived from my end and also cleaned the cache. Could you help. Also as per your screen there is floating menu with the demo logo, how can I change it ?

Perfect, I was able to do it and I like how it looks. Thank you!

Can you help me with two more things?

1- Mobile Theme
– I’ve tried several times to configure Tagdiv Mobile Theme and Official AMP for WordPress, but I haven’t been able to get it working. I activate them, but I don’t know how to configure them.

2- Lockers
– Is there a way for free posts with the Email Locker and membership posts with the Subscription Locker to show a summary of the content without blocking the full content?

Or, is there a way to restrict free content, so that visitors can only see a certain number of free posts after reaching a certain number of free posts viewed through the Lockers?

Screenshot of my locker:
https://prnt.sc/iFvUx0ajY0aW

Thanks!

Hi, thanks for the reply.

My question is not about thumbnails in Flex Blocks.
I am asking specifically about the Featured Image size in the Single Post Mobile Template.

Does selecting “Full – 1920px” in the mobile template include the full 1920px file in the HTML srcset? Or does the Mobile Theme generate its own srcset?

I need to know which setting guarantees that Google Discover sees an image ≥1200px in the HTML.

@Calin, You know what’s happening, the theme is ignoring the post made for mobile (there’s a separate mobile theme), you can see it here: https://ibb.co/DgpbbLbT. It loads the desktop page on the phone, analysis: faint blue header and an ad like this (it’s for desktop), there’s no ad on mobile, the ad is only for desktop. Remember you told me to activate this? https://ibb.co/Rkjbv6bP It’s activated. Even so, the theme is loading the desktop theme on mobile, it doesn’t know how to separate them and isn’t separating them. The cache is correct https://ibb.co/JRVBbRqz it’s activated to generate mobile cache, look at this loading from https://ibb.co/TBT7jJLr, I mean, I did this last year, separate mobile theme, look at this https://ibb.co/x8c0yx07 everything is correct. I ask for a solution to fix this. You saw the performance is bad, horrible, because of this. I think the theme developer needs to create a plugin to redirect pages created on the mobile theme, so that when you open the mobile theme, you only open the desktop theme, and only the desktop theme, to avoid this mess. I’m asking for help; if you can’t help, talk to the person who created this theme and ask for guidance. I’m losing audience and rankings because of this.

I appreciate your suggestions and I will follow them. Thank you for reporting this issue to the theme developers. I hope they can fix it permanently in the next update, because mobile traffic is the most important. If it’s already like this on a VPS, I can only imagine how it must be for users on shared hosting.

I also forgot to mention that Google Fonts are significantly affecting performance. The theme depends on them, and they are adding about 37.8 KiB of render‑blocking resources in PageSpeed, as you can see in this screenshot: https://ibb.co/4H1PDGc

You suggested the OMGF plugin (https://wordpress.org/plugins/host-webfonts-local/). I installed it, but unfortunately it’s very limited and constantly shows messages encouraging you to upgrade to the Pro version to improve performance. The Pro version requires an annual payment.

I looked for alternative plugins, but most of them are also paid. My suggestion is something much simpler: please ask the theme developer to include an option to download and host the fonts locally directly within the theme, instead of depending on paid third‑party plugins. This would improve site speed and overall performance.

If you could also pass this suggestion on to the theme developer, it would help a lot.

Hello @Calin

I am writing to you after a deep technical audit that lasted two days, conducted by a Senior Infrastructure Engineer and Web Performance Specialist. We had to take this measure because our PageSpeed scores are stuck between 31% and 41% on mobile, despite running on a high-end VPS with persistent cache (Redis/Object Cache) and every possible server-side optimization.

Google has officially notified us regarding this poor performance, stating that our site is no longer a priority in search rankings due to failing Core Web Vitals. After a thorough investigation of the source code and database, we have pinpointed the root cause: The Newspaper theme is loading both Desktop and Mobile assets simultaneously on mobile devices.

Even with dedicated mobile pages (separate IDs), the theme “stacks” the entire desktop framework on top of the mobile one. This redundancy is killing our performance.

I need you to take this diagnostic to the tagDiv development team immediately. We need to know if and when a fix will be released. If this architectural flaw is not resolved, I will be forced to migrate to another theme or develop a custom one, as I cannot afford to lose my SEO ranking due to theme bloat.

Technical Diagnostic:

Problem: Mobile pages heavier than desktop pages
Date: 03/05/2026
Theme: Newspaper 12.7.5
Plugin: td-composer
Server: VPS Ubuntu — CyberPanel — LiteSpeed

CONTEXT
The site glostv.com uses the Newspaper 12.7.5 theme with the td-composer plugin and has a system of separate pages for mobile and desktop, where each version was built individually in the Newspaper visual editor (tagDiv Composer). The site owner reported that pages on mobile are significantly heavier than on desktop, even though there are separate and optimized mobile pages already built.

MOBILE SYSTEM ARCHITECTURE
The following pages were created as mobile templates inside the tagDiv Composer itself and are marked in the database with the flag tdc_is_mobile_template = 1:

ID 7584 — tv ao vivo Brasil (mobile version)
ID 7617 — POPULARES TOP (mobile version)
ID 8700 — Estados (mobile version)
ID 8872 — Homepage (mobile version)
ID 9944 — Política de Privacidade (mobile version)
ID 9948 — Termos de Uso (mobile version)
ID 10581 — Sobre Nós (mobile version)
ID 10597 — Política de Cookies (mobile version)

TECHNICAL PROBLEM IDENTIFIED
Problem 1 — td-composer loads assets WITHOUT any device distinction

Confirmed directly in the file:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php

Line 362 — Composer JS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_js_composer_front’, 1000);

Line 430 — Full Newspaper CSS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_front_css’, 1001);

Line 744 — Full theme JS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_front_js’);

None of these functions have any device check. They load for both desktop and mobile equally, without any condition whatsoever.

Problem 2 — The mobile engine loads ON TOP of the desktop engine

Confirmed in the file:
wp-content/plugins/td-composer/mobile/functions.php

Line 149 — Mobile CSS loads ON TOP of the desktop CSS already loaded:
add_action(‘wp_enqueue_scripts’, ‘tdm_load_front_css’);

Line 173 — Mobile JS loads ON TOP of the desktop JS already loaded:
add_action(‘wp_enqueue_scripts’, ‘load_front_js’);

Line 184 — Mobile specific script loads ON TOP of all previous ones:
wp_enqueue_script(‘td-site’, TDC_URL.’/mobile/js/tagdiv_theme.min.js’);

Problem 3 — The flag tdc_is_mobile_template does NOT remove desktop assets

Confirmed in the file:
wp-content/plugins/td-composer/includes/tdc_state.php

Line 42:
private static $is_mobile_template = false;

Line 202:
public static function set_is_mobile_template($is_mobile_template) {
self::$is_mobile_template = $is_mobile_template;
}

This flag only serves to let the visual editor know it is on a mobile page. It does not execute any removal of desktop CSS or JS. It is purely an internal state variable with no effect on asset loading.

Problem 4 — Proof: Zero wp_dequeue for mobile anywhere in td-composer

I ran the following command directly on the server via terminal:

grep -r “wp_dequeue|deregister” wp-content/plugins/td-composer/ -n | grep -i “mobile|desktop|css|js”

The only result found was the removal of Visual Composer scripts in the backend administrative editor, not in the frontend. Throughout the entire td-composer codebase, there is not a single wp_dequeue_style() or wp_dequeue_script() instruction conditioned on mobile device detection in the frontend.

WHAT THE MOBILE BROWSER IS ACTUALLY DOWNLOADING
When a user accesses the site from a mobile device, the browser downloads all of this before rendering the mobile page:

From the desktop engine (which should NOT load on mobile):

Full legacy CSS of Newspaper
td-composer frontend JS (desktop visual engine)
tagdiv_theme.min.js desktop version
td-cloud-library CSS
td-standard-pack CSS
td-multi-purpose/style.css
Desktop version fonts
From the mobile engine (which loads ON TOP of the desktop):

Newspaper mobile CSS
tagdiv_theme.min.js mobile version
Mobile specific scripts
Fonts loaded again
The mobile browser is downloading the complete Newspaper framework twice. Once for the desktop layout that is discarded and once for the mobile layout that is actually used. This directly explains why mobile pages feel heavier and slower than desktop pages. DIRECT QUESTION TO SUPPORT
Does td-composer 12.7.5 have any native mechanism to remove desktop engine assets—specifically the functions load_front_css, load_js_composer_front, and load_front_js located in td_wp_booster_functions.php—when the page being served is already marked with tdc_is_mobile_template = 1 in the database?

If yes, in which file and on which line does this asset cleanup occur?

If no, when is the development team going to release an update to fix this? It is unacceptable that a high-end theme like Newspaper forces a mobile device to download the entire desktop framework AND the mobile framework simultaneously. My server-side analysis confirms that even when using dedicated mobile pages, the theme simply “stacks” assets instead of “swapping” them.

This redundancy is causing a massive performance overhead and killing our Core Web Vitals. We have separate pages for a reason, and the theme should NOT be loading desktop junk on a mobile-dedicated template. We need a clear position on when this will be resolved so that tdc_is_mobile_template = 1 actually triggers a wp_dequeue of unnecessary desktop resources.