Search Results for 'amp'

A good thought for improving landing page visibility for non magazine portals using this theme. Note that on “most” magazine sites there is no semantic need for an H1 tag on the “cover page” as there is no unique content, as it’s often dofollow links to the story which has H1 tags and you want THAT page to be indexed under the title of the story as the canonical link and not the same content on home page (I’ve been doing SEO since 1996, fyi, professionally). Often with the “home page” the H1 tag is actually used on a slider to focus on the ‘featured’ information; so for example if you have a slider loading slides via ajax, the “visible slide” would have H1 tags for the “featured” element, or headline, and that would become the H1 tag for the front page as primary element.

On a service portal like Yoast, which is not a news magazine, there is no “featured” element, and so the logo is an appropriate place to use the H1 as he is optimizing for YOAST as well as ‘website optimization.’

So, you may want to check usage of the “slider” options first, which are commonly used for this particular theme and which may have the H1 tag you’re looking for.

Adding a conditional logo tag for only the home page might add bloat to the theme for that purpose.

Also, for “alt tags” — remember you need to actually add the alt tags to your images on upload with the media manager. My sites have proper alt tags on the home page, and have since day one, so not sure where you’re seeing those “missing.”

Hope that contributed to the discussion a little bit 🙂

Chris

(pardon the mix of ” and “” here …. in one of those moods today where lazy to hit the shift key 🙂 )

https://lh5.googleusercontent.com/-G8xpXP6s3IY/UtsFtsj_EBI/AAAAAAAADNc/j0bHriLt4l4/w1597-h647-no/Cart+view2.jpg

Hello，
I certainly know I did not buy the theme, I’ll show you sample, to see if I can not buy this theme is change

Hi, Radu
that would be awesome. I switched from using the child theme so as to not impact my pagespeed adventures, and so the custom CSS I put at bottom of style.css didn’t have an impact in the way the child/style.css did. Being able to tweak a few things here or there with either a custom.css file, or perhaps more appropriately these days a “hook” to drop some code in the head at bottom before the body tag (Woo Themes does this fairly well, btw; they have all these little ‘hook’ locations to drop in code, although it does add a slew of if/then crap; disclosure we’re trying to ramp up your theme to replace Woo Canvas!).

So for us to be semi-done and in full “go mode” my laundry list of stuff needed is simply:
1) Google async alignment in top bar
2) websafe fonts option – which would save me hacking that one
3) custom.css injection hook in head, to over-ride couple of minor things (like making the author box bio text size smaller, when making the post side larger so the author bio isn’t over-large from the base adjustment)
4) not critical; but option to have a local image for author box (add new user meta field for ‘author image’ — we used to do this on our in house theme, not difficult) to not pull gravatar and save some bandwidth from external site — if you wanted to wow the kids, you could add a “grab my image from gravatar” option 😉 Peeps love the “automagical” stuff.

Otherwise, for us — you’re done! I’m hoping the v3 won’t introduce new issues, but right now we’re very happy.

BTW: for ‘web safe’ fonts, Adobe came up with some really quite brilliant ‘stacks’ of the best font mix to use across Mac, Windows, iOS, Android, et al. They can be found in Dreamweaver, and possibly their help system – but if you need those, just let me know. Much nicer than the old skool ‘Helvetica, arial, sans-serif’ stack. 🙂

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

Hi, Anna
we’re running the latest “stable” release from November. The current January version is an “edge” (or “Beta”) which is on different development track. So, hoping the stable version will be updated end of January with some of the new fixes.

Since our main sites are mission critical we dialed back all the filters server wide to just the CoreFilters minus one lazy load element (have an over-ride to lazy load images on page load and not on scroll as that did weird things).

Originally tested with a “full set of best choices for WordPress” but we’d see that something caused conflicts and so doing side by side speed of loading tests, most of the time the pages would load more quickly with mod_pagespeed OFF, which didn’t make much sense.

Now, I’m testing the filters sort of case by case, then testing the “mix” of elements (e.g., fonts, adsense, grvatar, addthis/social buttons) with each option, trying to use as few as possible to not actually slow things down (meaning why have mod_pagespeed do something which doesn’t actually need to be done — 10 extra filters adds some latency somewhere, although if done pre-cache not a biggie “in theory”).

It’s also worth noting I hacked the addthis plugin to add the “async” method which is not built-in (stupidly); which can be found in one of my other posts.

The adventure continues on Saturday!

Also note that some “master filter” settings enable sub filters, as so:

ModPagespeedEnableFilters rewrite_images (apache)
in the configuration file. This is equivalent to enabling
inline_images, recompress_images, convert_png_to_jpeg, and resize_images.

And then recompress_images is a master ‘group’ filter set for the following:
This is also a group filter, and is equivalent to enabling: convert_gif_to_png, convert_jpeg_to_progressive, jpeg_subsampling, recompress_jpeg, recompress_png, recompress_webp, strip_image_color_profile, and strip_image_meta_data.

So as you can see there are
master group >> sub master group >> end filters part of sub-master group

hence the phrase “tricky” 🙂

I am testing the master groups first to find what doesn’t work; then sub-groups, then down to specialized sub-filter settings.

• This reply was modified 12 years by simchris.

photo sample link

https://lh3.googleusercontent.com/-byiG6ZQ7Ceo/Utd22ijDKJI/AAAAAAAADMw/TEK-skadG2g/w1597-h751-no/Cart+view.jpg

web site link

http://planetshine.net/demo/pandora-woo

I second this emotion. I was actually trying to make the post story titles 48px and was limited to the 40px. I suppose simple fix is just adding css adjust for that at bottom of the main style.css ?

Since we’re not using a child theme, where *is* the best place to insert custom CSS ? I don’t think there is a hook to put custom style inline with the head to override the main style. I tried to over-ride something by putting at bottom of the main style.css, but I guess I need to do mods for each viewport section.

photo sample link

https://lh3.googleusercontent.com/-byiG6ZQ7Ceo/Utd22ijDKJI/AAAAAAAADMw/TEK-skadG2g/w1597-h751-no/Cart+view.jpg

web site link
http://planetshine.net/demo/pandora-woo

actually also anyway to make the sizing huge but responsive? just noticed looking at the responsive layouts. the text which has been adjusted by the PX is much larger than the Headings

Hi,
you might try “The Unarchiver” which is free in the Mac app store.

This does support the 7-zip file format.

What I use personally on BOTH my Macs and PCs is the robust, awesome and super useful WIN-RAR, which is $29 but will decompress ANYTHING:
http://www.win-rar.com/download.html?&L=0

🙂

• This reply was modified 12 years by simchris.