This has been happening over the past week. May take about 15-20 seconds for them to show.
BTW, not sure if this helps, but the social media icons initially appear as Asian (chinese?) characters in Chrome, Edge and Opera.
In FireFox they initially appear as boxes.
The other icons (search and down arrow menu) initially appear as boxy items in all browsers.
Likely because the font is loading ‘after’ everything else to speed up page load.
Only way to really fix that is complex
a) either load the font in header up front
b) convert the font elements to base 64 and include inline in the code
c) Another option, would be to unhook the theme font, and instead load the ‘font awesome’ font off their CDN, which would make it more likely to have been cached by a visitor – and hence load faster even though 5x the size of the ‘slimmed’ version included with theme
Just food for thought.
Welllllll, examining a couple pages through Firefox’s Developer tools, I get the following as taking 15 secs to load.
…/wp-content/themes/Newspaper/images/icons/newspaper.woff?14
Anything from the Newspaper Crew?
Hello,
Please check your host settings and try to change a few things around. Try to switch from a managed hosting plan to a standard hosting plan, try to disable some optimization tools from the cpanel, try to remove any weird code in the htaccess. If you did not add anything to the htaccess and you see weird code there, try to delete all of the content and then re-save permalinks on any other setting besides the default one.
Try to disable plugins as they can also affect the proper functionality.
It can be a large number of things and all these steps must be taken to identify the problem. Sorry but there is no simple way of debugging an issue.
Thanks.
Thanks Bogdan and Chris.
Once again, Cache problem…The bane of my existence! Uggggghhhhh.
Still can’t wrap my head around the issues I have with Cloudflare’s
No Query String vs. Ignore Query String vs. Standard.
Have had it at ‘Ignore Query String’ for a couple months now due to problems incurred using the others. Remedying this more current problem involved setting it to one of the others for awhile before setting it back (that is, after flushing the cache everywhere I could find).
