sailors
Forum Replies Created
-
Forum: Plugins
In reply to: [Yoast SEO] sitemap_index.xml Mobile Usability issueThank you for your reply.
I didn’t intend to force indexing the sitemap but somehow it ended up like that and I don’t know how that happened. The errors showed up all of the sudden. What steps should I take to fix them?
I once deleted it and resubmitted right away. Maybe I should wait a day or two then resubmit? would that help? or should I wait until Google removes it in next few weeks?
Thank you for your confirmation, Nastia.
Glad that I did the right thing but it just looks strange.I configured my Cloudflare for a while ago, think it looks different from back then. Here’s my current setup,
https://snipboard.io/YHET8N.jpgI turned off Cloudflare’s Rocket Loader and the Cache Everything Page Rules, purge Cloudflare cache and clear Hummingbird cache, and cleared browser cache on every single pages by ctrl+shift R key, then it finally stopped repeating Asset checking files process and I can now see all the assets on the page.
I think the Cache Everything Page Rules is the number one suspect for this issue. Every time I revise my content I have to turn it off first.
Hi Anton,
Please let me know when it’s ready. I leave the WebP option off for now.
There is an orange exclamation marks next to the code, unknown property ‘font-display’.
I looked up online and saw it might not affect performance much but if you know about it let me know, please.BTW, I use this tool to create critical path CSS,
https://jonassebastianohlsson.com/criticalpathcssgenerator/and paste the generated code into Autoptimize’s CSS inline and delay box.
I changed the path to full URLs and see the piece of code, font-display: swap; on my page source. I still get that performance test message.
Hi Anton,
This is what I get after the performance test,
Ensure text remains visible during webfont load : 0 score
status : Your page is not using font-display rule when loading the following web fonts.Font URL :
https://cdn.jsdelivr.net/fontawesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
https://fonts.gstatic.com/s/josefinsans/v14/Qw3FZQNVED7rKGKxtqIqX5Ecpl5te10h.woff2
https://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN_r8OUuhp.woff2I’ll change the relative paths to full URLs as you mention. That’s why I’m getting the message?
Thank you for your help.
I purged everything in Cloudflare, cleared cache in Hummingbird and Autoptimize but it didn’t fix the issue.
Thank you, Gerard for your reply as well as answering my other Cloudflare question.
Thank you, Anton for your prompt advice. It looks all fine now.
Can you please check all those pages visible again? I cleared FB and Autoptimize cache, then needed to refresh my browser a couple of times until they are visible.
I first updated the Contact Form 7 plugin, then WordPress 5.3. That’s all. I saw those warnings after updating them.
Thank you for your advice. I couldn’t log back in after the issue but by removing those two that you mentioned I’m able to now.
However, the site still has some issue that pages other than home are not showing. Can you please check if you see those other pages? If not, what would be causing that?
Thanks, Anton.
I found that in Pingdom speed test. Yes, I use the free version of Hummingbird. I will leave those options default.