Search Results for 'mobile'

Hi again,

this issue makes it really inconvenient for the users on mobile….
I would like the visitors to be able to see the sub categories/sections of the site easier. Most of the people click on the word/category name, not on the “>” sign.

This way (when visitors don’t click on the “>” sign) they can’t see directly what sub-categories the main category offers.

If I create custom static pages and redirect the product categories in question to the new page urls, the visitor will not’t immediately see all sections, what he/she would actually expect to happen, but will have to visit a page and scroll down in order to see what’s on it.

Is it possible to make the words/main category names unclickable (in general) so that on mobile the user will have to click on the “>” sign in order to see something happening?

I already have this figured out. I do need to compose page contents for mobile separately or remove the plugin if I want to show the same content as the desktop view.

To do it quickly, I just used the Categories for Mobile Menu.

Now, 1 more question. How can I show Recent Post of certain category on mobile theme content? Thank you

Did you test your pages with F12 to see if errors?

Google did start some big changes in August, moving stuff around, converting a lot of properties to mobile first (e.g., Google news undergoing transition to mobile first view even on desktop).

There was also update to the Automattic AMP plugin last month if using that, so change might have impacted something.

Also, as I understand it, not all pages get served as AMP versions by default since technically I think there is some usability threshold for it to get cached fully on Google’s edge CDN — but things change so much over there, hard to say.

I must add that the animation makes loading of images on mobile devices very slow. And I’m talking about a good few seconds here. You want the top images to load instantly, and those are the ones the visitor sees first anyway (above the fold). This is just my experience with it. 🙂

Ignore, I have made it work, but added a comment on another forum topic on how to remove some of the menu items as the same as main mobile menu

Wellll…. all our news is in Google News, and has been since 2005, without AMP 😉

And luckily AMP doesn’t create duplicate content issues, since the canonical link is designed just for that purpose and the AMP version links back to the real version to solve that (same way a print template does). With our old CMS on our big site, not using WP, and generating static shtml pages), we has static print and AMP pages, and both had canonical links, and the AMP template was built off the print template since there were not AMP plugins when we got started on that (and the main site didn’t use WP at that time, but now does).

For our news pages now (not using TD theme, but custom thing), we can load up the full news story with 2 images, logos, content, queries for related stories, etc., in 1.3 sec fully loaded. AMP version is quicker. But a scaled back print version would be just as quick.

All about the payload.

And with move to PHP7 + http/2 the speed will be even faster.

I guess we’re thinking over here that http/2 with a lean template would be better than AMP for user speed on mobile in the coming year. We’re playing with this anyway.

Doesn’t solve the page count issue — but of course Google wants you to run GA on AMP, and so that might even be the only truly workable solution for metrics on AMP pages.

Anyway — back to work before Labor Day holiday here …. cheers 🙂

Hey Chris, you bring up some very good points and for most parts I agree with you. I would be way happier without any form of AMP, especially since it could hurt SEO (double content). Since my website is targeting Netherlands and Belgium (written language is Dutch), the speed of the internet doesn’t really matter since we have both very good cable- as mobile connections. See the following:

https://www.iamexpat.nl/expat-info/dutch-expat-news/netherlands-has-fastest-internet-europe

The one major problem is when you’re content marketing products, which in return should deliver good DA-ratings (Domain Authority). The mobile pages that NewsMag delivers are working perfectly fine (with a few tweaks here and there). However, when trying to get content up in Google News, it’s more likely to happen with AMP-posts, simply because of the speed and simplicity they deliver. A normal page with cache gets loaded up in like 1.5 to 2.5 seconds, yet the AMP-version takes half a second or less, most of the time even lower than 200 milliseconds locally.

So to answer your question: No, the user experience doesn’t suffer when throwing AMP-pages out to just use the mobile version. Content marketing, on the other side, does in my current opinion. It also brings more maintenance and more chains in the line that could break.

Would the opposite work? For example the Social Icons, log in are part of the side full menu on a mobile, so I do not need those to show up on the top header menu? Thanks

Since amp ‘forbids’ client side scripting, it may be they are blocking anything being ‘run’ — or it may be that it runs first time, but then when cached on Google’s CDN for edge loading, the element script can’t run, as it’s not actually on the CDN.

There are folks doing stuff with Ajax with AMP for refreshing origin content; which is a bit like expiring the bucket on a CDN to refresh the local copy of content.

Personally, I’m of a mind, that AMP is an interim solution while wifi speed and phones play catchup. For instance, a new iPad PRO is more powerful than a 10 year old PC that HTML5 was built for.

In theory, one could argue that simply building your own print template with lean code, your desired custom elements like forms, or related post, or video, or whatever, could be ‘dressed down’ to lowest form like a print template, serve that for mobile and not even use AMP. Speed would be the same, especially if you’re already using CDN — and having a lightning bolt in SERPS doesn’t mean your page is better than everybody else’s page, just that it’s compatible, and might not even show up in SERPS, with all other things being equal with relevance, site age, content, etc.

Does the user experience suffer with AMP? Then why use it?

Questions for another time and place probably, but after nearly 2 years since the BETA, we’re kind of re-evaluating this for 2018, frankly.

Just more ramblings … 🙂

Hi lads
Same here
You keep saying that mobile won’t show the top menu.
If certain menu item is not that important to be placed in the main menu, it doesn’t mean it’s not important at all for the mobile phone users.
So how do we suppose to show it to the them?
Why not to have separate menu for mobie where we can stick all the items we need?

Otherwise it doesnt make sense at all.
Do yo uagree?

Thanks

Hello Nano,

Write a simple plugin for functions.php, and add your custom codes there. The plugin will auto put your custom code to the both main and mobile theme’s functions.php. So whenever you update the theme, you don’t need to edit functions.php file.

For style.css, you can use theme panel to add custom codes. You can force write the rule by adding an important tag.

For fonts, it seems you’re using Poppins bold for headlines and the default fonts for the rest of the site. You can create own.woff file for the Poppins bolt and use it with custom fonts file option in the theme panel.

Hope this will help you.
All the best

I think the amp endpoint function is related to changing the ‘endpoint’ — such as if you wanted /ac/ vs /amp/ or /mobile/ or whatever.

Sorry I don’t have perfect answer.

On another site, with a custom lean theme, we have it added to the /amp/ endpoints, but we’re using the venerable WP-Postviews plugin.

in this context, the function we have is this:
do_action( 'amp_post_template_head', 'process_postviews' );