We need the sign in though.

Thanks. We’re running into the same issue. Keeping our PageSpeed score optimal is priceless for search ranking.

Hi Bettina,

That’s the one I’ve been using, but since pages are cached unless they are updated the date becomes stale.

Do you have a JS code that can be inserted there that shows the date of the browser/device instead as it will stay up to date and then it won’t matter if the whole page is still cached worldwide.

Two related questions

What happens in this situation?

b) Featured image (>1080px) => 1920×0 + Retina

Normally I have 1920×0 + Retina selected as thumb, but since 1920 is already twice the size of what is needed (1080px), should I also turn on Retina?

So I’m thinking about what will happen if I turn it off (and after regeneration)?
– On Windows: 1920px is served?
– On a Mac: 1920px is served as well, which roughly 90% of what is needed for full (2x) Retina and may be sharp enough?

1) I guess what I’m asking is: If the Retina button is switched OFF on for 1920×0, how do Macs process the data? Will they still display a resolution higher than 1080px, simply because the data they have in the image (1920×0) allows for it, or will it miss a certain tag or instruction to display it at its sharpest, retina resultion?

2) Alternatively, I could serve 1068×0 images to windows (1.2% smaller than full 1080 – might possibly lose some sharpness) and activate Retina. What are your thoughts on this?

Thanks Calin for the answer.

Glad to see I’m on the right path.

Still hoping that device-specific image resolution will make it into a future build. Pagespeed score will soar. 😉

I’ll try with these settings and after that do comparison with a few plugins. I’ll try EWWW, as well as the Shortpixel Plugins, so good to know that overall I’ve set up things correctly.

Thanks Calin.

On the hamburger menu background: Is there a way that we can add a class to that DIV that holds the background image on the mobile hamburger menu/search menu? I don’t think we can set a defer value using CSS and having to write JS to find it will likely incur even bigger penalties in PSI.

On the images on viewports such as mobile, being too big:

Do you mean loading the original template as a mobile template and swapping out those values in Flex Blocks? I’m try to avoid separate mobile templates, as it easily doubles my work and it becomes ever harder to maintain two versions.

Hopefully in the future a dropdown per viewport inside the theme will allow us to choose which size to load. 😉

Kudos on the theme, btw. It’s stellar!

Thank Calin.

Just an idea, but maybe good for later:

It would be good if when we write code in the current on-page CSS Editor we can add some kind of structured contents that would tell the system later to drop the respective CSS/JS code into into separate files.

/* ## CSS Viewport: Horizontal – Load: Sitewide ## */
css code

/* ## CSS Viewport: Desktop – Load: Homepage, Categories, Tags ## */
other css code

/* ## CSS Viewport: Desktop – Load: Single ## */
other css code

It would allow us to keep code in one place, and would be super versatile.
Devices only load specific code meant for their viewports, so it would cut down on half or more of the CSS code.

A similar structure could then be used for inline generated code.

A later step could be to have a function go through the code of the page/template and build separate css files for each device, and/or type of page.

It would cut down on code, reduce the cost of data transfer both for publishers and for the audience and thereby improve PageSpeed scores a lot. I’ve noticed that typically 60-80% of CSS and JS code that is loaded isn’t really used on the page or on the specific viewport.

This would fix all of that and we could get Newspaper achieve 100 PageSpeed score on Mobile with the responsive design, without having to complicate matters mobile/AMP templates that lack functionality or brand-specific styling.

Let me know how I can be of help on this or beta.

Best to post PSI screenshots so people see what you see ;-).

Likely reasons:
1) You have articles loading through AJAX on Flex Block 1 elements. Make sure to enable caching 5 minutes or longer on those blocks. It’s in the bottom of filter or layout or so.
2) Make sure to run an object caching plugin such as REDIS or MemCached. It will store all those expensive lookups on disk in memory instead.
3) Serve your site through a better protocol such as http/2 or QUIC. It will help get the data quicker to the audience.
4) Look at Google PageSpeed Insights on how to further improve your performance score.

Good luck

I have enabled caching on the flex blocks so it’s fixed on the home page.

The single article pages are still generating admin-ajax calls to count page views. It might be good in a future version to only trigger that call after maybe like 50ms or so after the page has fully loaded?

How could we do this?

[SOLVED]

I found a solution so I’ll share it with the community.


:root {
--color-page-bg: lightblue;
}

.post, .td-main-content-wrap, .td-category-grid, .td-container-wrap {
background-color: transparent !important;
}


In this example I’ve set the background in the CSS to be lightblue.
Then I removed the fixed colors in the theme for the 4 elements that have them defined.

Actually, I also see it on .td-container-wrap and .td-main-content-wrap …

Thanks Anamaria,

Which security plugin is recommended with Newspaper Theme?

Hi Anamaria,

I checked all and I don’t have the deny statements in the .htaccess, nor the other conditions, but I found the reason, which may help other users as well.

I am using iThemes Security for the site, likely one of the best security plugins.

When I disable it, the WP Editor works, likely due to this setting:

Disable PHP in Plugins
Disable PHP execution in the plugins directory. This blocks requests to PHP files inside plugin directories that can be exploited directly.

I don’t really want to reduce the security of my website, so what sort of .htaccess override settings should I place in which folder exactly?

@ninjaray, @cooperdevon, (how) did you get this resolved?
I’ve been having the exact same problem.
Never have been able to open the WP Editor inside TagDiv Composer.
It keeps on spinning and console has the 403 error.

I’m on a LiteSpeed Server, not NginX. All .htaccess setting as in the linked to pages in the forum, 10M setting, all server requirements met.

Are any of you running multisite by chance?

2 follow-up questions.

a) what about content that is behind a paywall, will that show up in search?
b) which file would we go into to filter things out?

Hi Bettina,

This is a sample with the demo articles.
The home page consists of a sample of each category.

Each category will be displayed like this, one under another.
So, 6 rows in total. Each category row will have 3 articles shown.

https://imgur.com/a/ztMsTOV

Since I’m building up this site and social media presence I’ll be publishing 1-2 articles per day so it will take a bit of time to fill up all those slots on the home page.

So where there is no article yet I want to display maybe a fixed article with always the same image. Sort of like a placeholder, but that entices the audience to let us know exactly what content they like to see.

So I’m thinking about having one article like that but trying to find a way to show it up wherever there are no 3 articles in each row yet.

Thanks Bettina,

I’ll rebuild that page first since I’m launching tomorrow.
For the second issue I’ll provide additional details early next week.

Have a good weekend

I want to acknowledge the TagDiv team that got back to me with answers to a lot of my questions by email.

I will post the solution here so other people who have a similar issue can be helped as well without needing to ask the questions again.

To see a list of all the posts and which template they use, add this to your url
/wp-admin/edit.php?post_type=tdb_templates&orderby=tdb_template_type&order=asc

It might be good to bookmark it somewhere 😉

Thanks team!

[SOLVED]

• This reply was modified 3 years by chrisfoxatx.

Yes. And that’s fine.

Just query 4, but depending on the viewport show only 4, or 3, or 2, or 1. Query 4, hide what isn’t needed.

SUGGESTION:

It might be good for TagDiv then to automatically set CANONICAL names for each generated page in the code so those template files do not get indexed by the search engines.

Most of the users will have no idea how badly this can hurt their SEO, and how to fix it until after it has already happened.

Sorry, but this is not “support”.

It’s basically the same support answer template. Using support as a way to push towards custom development. We aren’t making difficult support asks.

It would be good to say, at least go into this or that template to make a change, or look in this database table.

Quite disappointed.

FYI. Ending each support sentence with an exclamation mark either after Thank you for understanding! or Thank you! from a pure communication practice (I am a communications coach) comes off as extremely condescending and arrogant when no solution has been offered, and is a passive-aggressive way in trying to instill a feeling into the user as if he should already be that understanding or thankful for the non-answer.

It might be good to have someone well-versed in communication and customer support to brief the team on goor practices and placing the customer first.

Respectfully!

FYI @ncalex

• This reply was modified 3 years by chrisfoxatx.
• This reply was modified 3 years by chrisfoxatx.

Of course a title is set for an element.
Maybe it should be added to the to-do list then????

I’m sorry but it seems like a lot of these “support” replies are simply “No can do. Thank you!”

Maybe at least point is in the right direction as to how it COULD be done. Not everyone has the budget right now to go into custom developments.

And the way it is set up right now, with just a global number and not per module is ridiculous.

Try and show 4 posts which is great on desktop on a horizontal tablet with 3 columns and it looks plain ugly and not useful.

I’d hope you listen to your clients’ suggestions better. I’m planning on buying more licenses when we can receive adequate support instead of a friendly way of telling us to get lost.

Sincerely,