Search Results for 'cache'

thx, it was something in my cache, now it is ok after clearing it

No worries, i’ve found it.

If anyone is checking this thread out and is curious about the option. You can find it in W3Cache under ‘Page Cache’. Tick the box called ‘Preload the post cache upon publish events.’ and select the categories you want to purge.

Thanks! 🙂

• This reply was modified 11 years by Gee95.

No worries, Lucian thanks for the response.

Do you know if i can find the CDN settings to re-cache in Cloudflare or W3Cache? Never heard of that option before.

Thanks 🙂

Since this comes up a lot, I thought I’d list some of the plugins I use as standard fare on all our sites:

1) Thumbnail Upscale — this allows you to over-ride the stupid WordPress bult-in function to “disable” your servers natural capability with ImageMagik of “enlarging” your images to fit featured blocks/sliders.

2) Auto Post Thumbnail PRO — paid plugin which allows us to have some of our network content automatically pull from “first image in post” even if from our main hub, and make it the featured image. Awesome if converting to theme from OLD theme which used the TimThumb plugin.

3) WP-Optimize — awesome for regular optimization of dbase to clean house, on spam comments not deleted, trashed posts, and normal database clean up.

4) YOAST WordPress SEO — while we used to have an inhouse plugin for this, Yoast has done great job of putting it all together for managing meta data on global and per-post basis, setting up SEO for home page, and also OG tags for social media.

5) Awesome Weather Widget — we use this on our “state” and local news portals to add a nice local weather box to home page.

6) Limit Login Attempts — this should be built-in to WP, frankly. It helps stop people from sitting there and guessing user passwords or using a bot to hit it over and over. With IP blocking and tracking. Essential!!

7) WP External Links — in our case we need to make the majority of outbound links “rel=nofollow” and this does that automatically.

8) Auto-hyperlink URLs — we use this to control auto-linking of URLs in text, since we pull in a lot of content with visible but not anchor linked URLs in news text from our main hub. This makes all the links live, but also makes them rel=nofollow and open in blank/new window. Can also add external link icon if desired.

9) Simple Local Avatars — already noted in my optimization notes; this awesome little plugin allows you to load/cache GRAVATARS locally, as well as use local images for author pix, which will work on sidebar author blocks, author page, and in author box bottom of posts as it hooks into the main “author image” gravatar hooks; so anything which can read the normal WP gravatar image will work with this.

10) *lazy loading disqus” (not actual plugin name…) — we’re testing a recently launched plugin which uses Disqus API but loads element async and deferred and optimized to load after content and not slow down page. More later 🙂

Hope that helps somebody!!

Chris

Hm 🙁

That’s confusing! The error in the console doesn’t always occur.

But the problem with the fonts is still there – I just empty all caches (in FF, Chrome WIN7 and OSX). I also deactivate all FF und Chrome Add-Ons. In every browser the displayed fonts are not the fonts which are in the CSS.

WhatFont shows (default font)… (http://snag.gy/AZI14.jpg).

Thank you for all your assistance.

this is my htaccess file

<IfModule mod_deflate.c>
<filesMatch "\.(js|css|html|php)$">
SetOutputFilter DEFLATE
</filesMatch>
</IfModule>
# Pagespeed Module
<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>
# Pagespeed Module
# BEGIN Expire headers
<ifModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 5 seconds"
ExpiresByType image/x-icon "access plus 604800 seconds"
ExpiresByType image/jpeg "access plus 604800 seconds"
ExpiresByType image/png "access plus 604800 seconds"
ExpiresByType image/gif "access plus 604800 seconds"
ExpiresByType application/x-shockwave-flash "access plus 604800 seconds"
ExpiresByType text/css "access plus 604800 seconds"
ExpiresByType application/x-font-woff "access plus 604800 seconds"
ExpiresByType text/javascript "access plus 604800 seconds"
ExpiresByType application/javascript "access plus 604800 seconds"
ExpiresByType application/x-javascript "access plus 604800 seconds"
#ExpiresByType text/html "access plus 600 seconds"
#ExpiresByType application/xhtml+xml "access plus 600 seconds"
</ifModule>
# END Expire headers

<IfModule mod_headers.c>
Header unset ETag
</IfModule>
<IfModule mod_alias.c>
RedirectMatch 403 /xmlrpc.php
</IfModule>


This is a recent development this year with insights; kind of annoying; and why you get higher score with GTmetrix than insights score. With “responsive” design, images are often resized vs serving an entirely new image as traditionally it was actually faster since the server caches images, especially high request images. However, now the insights score is based on a “mobile user loading the content” as part of the “mobile first” movement, and so it seems there is going to need to be some kind of element added to all themes which load images much like the ad banners used to load the past few years prior to Google adding responsive ad units …

basically…
if viewport large = load big image
if viewport small = load thumbnail

Dumb thing is that in many cases, the larger image being loaded on mobile, e.g., iPad actually works better as a “resized” image, since it effectively makes a 640×400 96dpi image into a 340×200 200dpi image for retina displays by having larger pixel density when the large size is reduced on screen — hence why the images look so good on retina mobile devices without having to reload a “retina image…”

So….. stupidly, they are looking at “bandwidth” not “quality”…

Themes are basically going to have to be re-engineered to “by default” always make something like a 50% thumbnail and serve that on mobile devices.

Even stupider requirement because not all mobile devices have same viewport, and so it’s not practical for every page to constantly load 10 different size “featured images” based on viewport — this is what responsive design partially solved.

Upshot — you can live with suffering the warning for now — everybody is getting this — everywhere.

Not sure how TagDiv will address this, or if some super clever person comes up with plugin.

In our case we’re running mod_pagespeed and just updated last Friday (week ago), in hopes it would have solution for this as part of the “resize images” function (well, subset of “rewrite images”), and that isn’t even doing that with Google’s own technology!

(argh)….

Sorry for editorial. I started trying to deal with this April 1, and was super annoyed by the “actuality” of the issue.

Basically a featured image now has to be treated as an “ad module” and load a different size main image based on desktop v mobile. Show me any themes doing that right now. Nope. Annoying.

Hope that helped in some way …. main thing is to ensure the main images you’re uploading are as compressed as possible. I’ve been trying to make sure our larger images are no more than 25kb vs 32kb. If you have an image with 120kb that can be removed, it might be too big to start with.

No simple answer.