Search Results for 'header'

btw…
if you’re *not* using my example cache expiration file for htaccess … note most of the other versions forget to include expirations for font files (!).

So, be sure to look at that as one possible element for the font expiration headers (e.g., .woff).

As to the .js issue … that is odd … might be a setting on the main server for default expiration times, or some interaction with varnish cache time.

Hello, no. I’ve only header ad configured: http://s14.postimg.org/tkq9tb2s1/Cattura_di_schermata_673.png

This error appears also in wp-admin.

I’m using version 1.6, don’t want to install the new version at the moment as I’ve read about some probelms.

Not using any cache plugin.

I realise I cannot cache external resources.

What I mean is that before I put the settings in nginx/varnish etc. I have about 30 internal resources (.js, .css etc), however, now, I seem to just be left with these few resources, and for some reason they aren’t displaying browser cache expiry headers.

I have signed up with cloudflare, currently awaiting DNS resolution cache all my static assets.

Still does not explain why only some of the resources are getting cache expiry headers.

.td-logo-text {
   font-family: "Open Sans", sans-serif !important;
   text-transform: none; /* Removes uppercase format */
   font-size: 1.2em; /* Can use em, rem, px, or pt units here, set to preference */
}

.td-tagline-text {
   font-family: "Open Sans", sans-serif !important;
   text-transform: none; /* Removes uppercase format */
   font-size: 1.2em; /* Can use em, rem, px, or pt units here, set to preference */
}

.td-header-text-logo {
   margin: 60px 10px 60px 30px !important;
   /* These are default margins for the logo wrapper. In order - TOP RIGHT BOTTOM LEFT */
   /* Reduce the values currently at 60px to tighten the header up more */
}

Don’t forget, if you change something and it doesn’t show up on the site, add !important before the semi-colon to override conflicting styles from the theme stylesheet.

If you disabled all plugins then the header problem would have gone away. The only other explanation, besides a plugin conflicting somewhere, is if you have custom code that is conflicting somehow.

I see you also use WP Fastest Cache. Turn off JavaScript minification and combination in the settings. That *can* cause this issue. NewsMag theme documentation says not to minify the .js because it breaks the code. You can leave on all of the other settings for WPFC, including the css minification and combination features.

Be sure to completely clear the cache, including the CSS and JS (the bottom option on the admin bar WPFC menu) after you change the settings.

Let me know.

The problem with the header is a conflict.

Disable all plugins except those distributed with NewsMag. Re-enable your plugins one by one until the problem with the header returns. The conflict is disrupting most of the javascript on the site (search, theme social sharing popups, and probably the lazy load/infinite load on posts too, if it were enabled).

This may very well be a conflict caused by using NewsMag (built specifically for Visual Composer) with TCB.

Find the conflict and it may fix both issues. Won’t know how the excerpt issue is affected until that conflict has been resolved.

Good luck.

Thanks blogstyle header worked.

After 9 years with WordPress and 20 years with webdev… and the sticky post in this forum on how to upgrade the theme … um, yeah… I updated it with fresh version.

I have to do completely fresh version as I tweak the theme for some minor things like custom field for hit counter, remove the XLRPC thing from header, minify the style.css, remove the breadcrumbs from search template, and put in our custom functions for optimization and disabling some things like not loading the visual composer CSS on post pages, etc.

So, in theory all things being equal the 1.7 site should behave just like the 1.6 sites except with lazy loading on top.

And I never use child themes, and all files are uploaded with Linux/unix line breaks vs windows, etc.

(I’m an advanced user …. obviously …)

Hence my … what the hell, man reaction with the ENC site.

So… going to roll that back once I get couple more client things done.

Basically going to use our tweaked 1.6 version – same exact thing running musewire.

Of course the dbase for ENC is hideously huge, and 10x the size of musewire, but other than that …

We have 32GB RAM, 12 cores of XEON power, and dedicated gigabit switch in Class A datacenter (SoftLayer) … so, we’ve got the juice.

ENC has 512MB allocated to PHP. So… may I just say … “sheesh!” 🙂

@neotrope Thanks, Chris. As requested, here are the results with lazy loading off.

Zen Cache – Did not Re-Test
Gator Cache – Did not Re-Test

Page Speed Scores With Lazy Load Off – Speed Booster On
WP Super Cache – 56 Desktop, 43 Mobile
WP Fastest Cache – 62 Desktop, 41 Mobile
W3 Total Cache – 68 Desktop, 47 Mobile
No Cache – 62 Desktop

Page Speed Scores With Lazy Load Off – Speed Booster Off
WP Super Cache – 57 Desktop, 43 Mobile
WP Fastest Cache – 57 Desktop, 49 Mobile
W3 Total Cache – 71 Desktop, 51 Mobile
No Cache – 38 Desktop

Apparently, the Speed Booster plugin hurts mobile browsing across the board. The mobile scores with no caching was mid to upper 20s without and without Speed Booster. Speed Booster also seemed to hurt performance for all but WP Fastest Cache.

The lazy load feature actually had a positive effect on page speed when it was turned on.

However, the lazy load feature *looks* slower because of the delayed loading of above the fold content. Lazy loading content below the fold I understand, but above the fold content should always load first. Lazy loading seems to put structure ahead of content and that’s a bad thing no matter how fast things are loading.

Overall, 1.7 loads much slower than 1.5. As I said, my page speed scores for this exact site were all 85+ for desktop and 65+ for mobile with NewsMag 1.5, but 20-30 points lower for NewsMag 1.7. Tells me development is going backwards. No feature is good enough to justify slower loading times, unless you’re running a perfect 100/100 already. The scores I’m talking about include several AdSense ads per page in all situations.

There are two ways of looking at page speed; the most accurate is a page speed test where things are ranked evenly, even though I’m getting charged for Google Fonts that don’t appear anywhere in my theme (I switched it all to system fonts). But the most frustrating is the eye test; how fast the pages appear to load while you’re browsing. I was surprised during these tests to find that WP Super Cache (the good ole basic caching plugin by Automattic) made the content on the pages load quicker. The overall page load may have been slower or negligible, but when I opened any page, the first thing that appeared was the content, followed by the header, sidebar and background, and finally the ads.

I should also note that I was using the built in pre-load feature for the tests on WP Super Cache with lazy load and speed booster on, but I wasn’t using the pre-load feature for the tests included in this post.

@Alin_Vlad

I’m getting the same kind of issue after updating to 1.7.

From what I can see, the new version of the theme doesn’t support caching. I don’t the POS overbloated W3TC to cache my site, but what I use worked perfectly before the update. Some features of a caching plugin *might* need some compatibility fixes for each theme, but the theme is disregarding header expiration settings even, so I doubt it’s the plugin. WP Fastest Cache is what I’ve used with NewsMag and Newspaper with no issues.

All images are having to load fresh on every page load, whether it’s a VC template page or a standard single post.

My site background is also only loading once out of every 3-4 page loads. Not sure if that’s related to the slowdown or not, but there it is.

Site in question is http://bluestartimes.com.

• This reply was modified 11 years by Bryson T.

We just edited the header.php file to add the meta tag for author.

Using Yoast SEO plugin helps too.