Search Results for 'pagespeed'

Results from the Forum
simchris
tagDiv Member

tarquisti:

see – ask your hosting provider to set caching for your site: https://developers.google.com/speed/docs/insights/LeverageBrowserCaching

try using my expiration header settings in your .htaccess file
https://forum.tagdiv.com/topic/what-is-your-googlespeed-value/

try using an image optimization plugin for wordpress to make images smaller in size (compression) and then use the thumbnail redo plugin recommended by Radu

see: https://forum.tagdiv.com/how-to-make-the-site-faster/

tarquisti
tagDiv Member

Hello,

Installed the great template “Newspaper” and BAMMMM, SpeedPage is very bad:

Here a post: http://bit.ly/194FvaX

I am not an expert in changing Javascripts or CSS etc, so who can help me solve this problem?

Thank you..

simchris
tagDiv Member

@Marija1m1

See the threads on page speed. Follow Radu’s recommendations for how he got the demo theme to be 90+.

REF: https://forum.tagdiv.com/how-to-make-the-site-faster/ .

To save you having to read Everything on the forum:

Fonts can’t be optimized on your side or by the theme, as they live on Google’s website. Digg buttons are loading from Digg’s website. No way to optimize that. I don’t think sharedaddy is part of theme. You either have to load the font stuff locally and optimize CSS since Google “dings” their own stuff in PageSpeed (!) or switch to web-safe fonts (see my and other comments above on this topic).

For styles, you need to either minify if you don’t intend to modify for your site; or use a WP minify plugin. See my link to the site I use to minify my css and js code.

WP by default loads elements in the head and “enqueues” them to render the page. All WP sites will have a “render blocking code” in head error. For javascript (.js files) You would need to try the optimization plugin included with theme, or a WP plugin which moves the js to footer “elegantly.”

Hope that helped. 87 is a great starting point and that means you’re in the “zone of safety” as I like to call it. 85 or below is “bad” 87-89 is okay. 90+ is rockin’. 😉

Chris

  • This reply was modified 12 years by simchris.
Marija1m1
tagDiv Member

Hi I have 87/100 and I get these recommendations:
Suggestions Summary
Consider Fixing:
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:
http://smashinbeauty.com/
-includes/js/jquery/jquery.js?ver=1.10.2
http://smashinbeauty.com/
s/jquery/jquery-migrate.min.js?ver=1.2.1
Optimize CSS Delivery of the following:
http://fonts.googleapis.com/
ietnamese%2Clatin-ext%2Ccyrillic&ver=3.8
http://fonts.googleapis.com/
t%2Cgreek%2Clatin-ext%2Ccyrillic&ver=3.8
http://fonts.googleapis.com/
illic-ext%2Clatin-ext%2Ccyrillic&ver=3.8
http://fonts.googleapis.com/
0%2C700&subset=latin%2Clatin-ext&ver=3.8
http://fonts.googleapis.com/
ietnamese%2Clatin-ext%2Ccyrillic&ver=3.8
http://smashinbeauty.com/
aper/external/td-bootstrap.css?ver=1.7.1
http://smashinbeauty.com/
ent/themes/Newspaper/style.css?ver=1.7.1
http://smashinbeauty.com/
k/modules/sharedaddy/sharing.css?ver=2.7
http://widgets.digg.com/css/buttons3.css

any help or?

simchris
tagDiv Member

Hey BoredDaddy…
I will be offering this as a service again next year (WP optimization service) once we revamp our sites (ongoing); in midst of deploying new web server right now and sorting our memcache + eAccerlator + Google’s mod_pagespeed at server level. In midst of new server, and migrating our sites over, blah blah. The really arcane stuff is having mod_pagespeed convert images to Google’s new “in house” image format to load faster where it has a built-in image pyramid, with what we used to do for lowsrc (b/w image) to load as a progressive layer while the color image loads in. Wild stuff.

But to answer your question:
If you follow Radu’s little shortlist, that is a good “starting point” to get your site ramped up. His plugin does bunch of the stuff, and if you use that, turn off any whacky “phone home” plugins which are resource hogs, check your htaccess file for expiration headers, optimize your site images, and whatnot, you’ll be in good shape.

Use GTmetrix as a slightly more friendly and forgiving starting point for PageSpeed test, as it will actually tell you HOW to fix stuff. The Google version seems to be a little off, especially their latest version which catches all their own code as errors (!).

Marius
tagDiv Staff
SPEED - reply

Hello,

A. We have that plugin tagDiv Speed Booster that improve the them speed but is in beta and could have compatibility issues. That plugin move the javascript bellow. ALso you can move it by yourself if you want.

B. You can try it, make a test speed with and without facebook sharing option.

Also you can use page cache enable from W3 Total Cache plugin.

For more tips you can read in this topic is special opened for speed optimization https://forum.tagdiv.com/topic/pagespeed/

Thanks for your message

danielnn
Participant
SPEED - topic
#0

I just launched the new theme on my site.
http://www.theinspiration.com/

I get 85/100 on Desktop and 70/100 on mobile in GPS.
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.theinspiration.com%2F&tab=desktop

DESKTOP:
I really would like to optimize where I can. I use pretty large images on the site ( I know that), and I really would not like to compress them any more.

How do I?
A) Eliminate render-blocking JavaScript and CSS in above-the-fold content
– can I move javascript below the fold?

B) Leverage browser caching.
– I have FB and twitter buttons on the site, does this slow it down a lot?

C) Expiring Header.
– I am pretty confused about how much I could “save” By doing it

When I optimize something and test the site I get the same results.
Does GPS cache results?

simchris
tagDiv Member

try turning off jetpack to start with, and try making sure you have the mobile ads setup properly to serve the smaller ads for smaller viewports; also a “font” plugin it looked like was also impacting speed

when I ran GTmetrix on your URL got lots of stuff related to jetpack (wp.com stuff) … and nextgen gallery

http://gtmetrix.com/reports/www.thetechvoid.com/ENyQ4vso

Danrallison
Participant
#0

Hello,

Recently my mobile page has stopped working, and also page speed is quite slow.
website is http://www.thetechvoid.com

Can anyone help me?

Thanks,

Daniel

Marius
tagDiv Staff

Hello,
You can minify the HTML with W3 Total Cache and for js make it manually using this tool http://closure-compiler.appspot.com/home

Another things, optimize your images add this filter in function.php
add_filter( 'jpeg_quality', create_function( '', 'return 60;' ) );

Also you can read more tips here: https://forum.tagdiv.com/topic/pagespeed/ or search on our forum.

Thanks for the message!

pings
Participant
#0

Hey guys, IÂŽm still having problem using W3 Total Cache Plugin.

When I enable Minify JS, my background and “load more” button stop working.

IÂŽm having this problem since older versions.

My site is too slow, I changed from Godaddy to Hostgator and ItÂŽs still the same.

IÂŽm getting 62/83 points in Pagespeed, so I really need to do everything possible to make it better, including minify JS.

Please, what should I do?

website: http://emagrecersemdieta.com.br

thanks again!

BoredDaddy
tagDiv Member

@Christopher @Radu
Hi Guys,
Is there anyone who is willing to help me with my site optimization?
I use Google Speed Service but i’m getting very bad speed results 🙁
59/100 mobile and 76/100 desktop
We moved to VPS2 sever but still results are very bad!
Can anyone help me to optimize my site?
Url: http://www.boreddaddy.com

Thanks in advance,
Alex
CEO & Co-founder
Bored Daddy

GZAM
tagDiv Member

@Radu – thanks for font info – I’ll give it a try. As far as fonts go, I like web safe fonts – more of a design practice/preference than technical argument though.


@vidapropria
– with images – I got in the habit of using GIMP to compress my images before I post them – the utility is free and I found it by reading the following Google best practices doc (I am not sure what the rules are in this forum about posting links – but I figure a Google best practices link is OK)

for blogs – of course the images need to look good – but certainly don’t need to be over – say – 50k in most cases for featured images – I try to keep them under 30k as a general rule…(again – just my 2 cents)

here’s the Google link

https://developers.google.com/speed/docs/best-practices/payload#CompressImages

simchris
tagDiv Member

vidapropria
1) reduce image sizes either by running compression plugin and/or adding compression factor to your functions file
2) faster server account, if you keep seeing “slow response from server” error — that was a [!] item on your last report speed check — nothing can be done about that with the theme, or in WP; that is how fast the account you have and your hosting provider is responding to ping/start showing the page. For example if you have a $5/month account, upgrade to $10/month account (I’m just using that as example). Low cost accounts are usually on a machine or VPS being shared with 1,000+ other sites. Slightly more costly hosting accounts give more resources to each site, by sharing the resource pool with fewer domains.

Verify deflate/gzip working; remember this only serves up faster versions of your content, but doesn’t optimize them prior to that. I think I saw a 100K image file in your last report … that is waaaaaaaaay too big. Try using smushit plugin and regenerate thumbnails to see if that helps? (Backup images first as changes to images on server will be destructive — meaning they are changed and cannot be unchanged).

Also, for testing if you’re using a child theme, be sure to try NOT using a child theme to see if that gains you a point.

However RECOMMENDED:
1) optimize images before/after upload
2) look at better hosting – if you keep getting “slow to respond” error from Google — no way around that on your side.
3) test without using DISQUS, as this does slow things down. We stopped using it for that reason. We’re leaning toward phasing out comments on most sites, per industry practice now that most comments tend to be trolls and arguments (see: CNN for example). Any comments plugin really slows stuff down on WP. Unless you gain ad revenue from 10,000 visitors per day, it’s not really an essential plugin, and more of a glamour thing (in my opinion).
4) turn off all jetpack stuff for speed test — anything that connects to the WP/Automattic mothership adds latency.

Hope that helped 🙂

————–
as an aside on pagespeed errors:
I’m actually dealing with even more arcane stuff like how to enqueue the parent Theme’s style sheet in the child Theme’s functions.php, to bypass the annoying @import not recommended error from Google which the Automattic folks seem to think is a non-issue. I will post my efforts on THAT noise if anybody cares.

[ UPDATED ]
I just ran your GPS test, and saw you’re up to 82/100 desktop. So, looks like you’re making progress. The images issue is the next thing you need to resolve. You’ll have several points for that, as reducing the footprint of your images speeds up page (e.g., if you go from 300K to 150KB; that’s 50% less time loading images!).

For the minification stuff… note you would need to use a plugin for that (WPminify) although this has some issues; -or- you need to manually minify SOME resources which are not already reduced in size. RADU doesn’t minify all the code as developers have a hard time modifying code if they can’t read it.

So, if you knew there were a couple of large CSS/JS files you might want to minify, you can easily do that using an online tool (I use this one, although it won’t work with IE11/Win7 properly … use Chrome or similar: http://refresh-sf.com/yui/ )

Basically, “minification” of CSS and Java/js files removes the extra spaces, comments, and line breaks to make file “more compact” … so if you had a 125Kb CSS file, by removing all the spaces, line breaks, comments, it might end up being 100Kb, which is the kind of reduction that PageSpeed looks at — the idea being if you had 5 files being loaded on page and you reduced all of them by 20kb – well, that’s 100Kb and is larger than what website developers like me used for the entire page and graphics 10 years ago (we used to shoot for 50kb max page load, if you can imagine that!) …

  • This reply was modified 12 years by simchris.
vidapropria
tagDiv Member

Result PageSpeed 77 – 100 (desktop)
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2F50.97.105.190%2F~cidad259%2F&tab=desktop

URL – http://50.97.105.190/~cidad259/
Example code .htaccess


# BEGIN W3TC Browser Cache
<IfModule mod_deflate.c>
    <IfModule mod_headers.c>
        Header append Vary User-Agent env=!dont-vary
    </IfModule>
        AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
    <IfModule mod_mime.c>
        # DEFLATE by extension
        AddOutputFilter DEFLATE js css htm html xml
    </IfModule>
</IfModule>
# END W3TC Browser Cache

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /~cidad259/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /~cidad259/index.php [L]
</IfModule>

# END WordPress

<IfModule mod_rewrite.c>
ExpiresActive On

# Favicon (cannot be renamed)
  ExpiresByType image/x-icon              "access plus 1 week"

# Media: images, video, audio
  ExpiresByType audio/ogg                 "access plus 1 month"
  ExpiresByType image/gif                 "access plus 1 month"
  ExpiresByType image/jpeg                "access plus 1 month"
  ExpiresByType image/png                 "access plus 1 month"
  ExpiresByType video/mp4                 "access plus 1 month"
  ExpiresByType video/ogg                 "access plus 1 month"
  ExpiresByType video/webm                "access plus 1 month"

# CSS and JavaScript
  ExpiresByType application/x-javascript    "access plus 1 week"
  ExpiresByType text/css                  "access plus 1 week"
  ExpiresByType text/javascript		  "access plus 1 week"

# Webfonts
  ExpiresByType application/vnd.ms-fontobject "access plus 1 month"
  ExpiresByType application/x-font-ttf    "access plus 1 month"
  ExpiresByType application/x-font-woff   "access plus 1 month"
  ExpiresByType font/opentype             "access plus 1 month"
  ExpiresByType image/svg+xml             "access plus 1 month"

</IfModule>

What is missing to get to 90?

simchris
tagDiv Member

Vidapropria
ironically your IP seems hosted in the same network as us (SoftLayer/IBM).

YOu may find this additional info useful
report for your test page:
http://www.webpagetest.org/result/131209_97_1PRT/

simchris
tagDiv Member

Hi, vidapropria
don’t forget you still need to set expiration headers, and possibly get a faster hosting account – 4 seconds response is pretty slow on top of the page loading time.

You might try loading my suggested “expiration” data for your htaccess file (see other post on this topic), which goes at bottom of htaccess AFTER the wordpress stuff.

Looks like you need to
1) speed up server time to < 2 sec. if possible (try using a speed test closer to your country, if your site is regional and not international: use Google’s webpagetest.org and choose location closer to you)
2) set expiration headers – this is MANDATORY for page speed! (SEE: https://forum.tagdiv.com/topic/what-is-your-googlespeed-value/ )
3) further optimize images using an image plugin like (WP Smush.it – or similar); backup images before running any plugin on your images, so that you can restore if unhappy with results.

Hope that helped. Try the expiration headers data for the htaccess file first. It really really helps!

  • This reply was modified 12 years by simchris.
vidapropria
tagDiv Member

I installed the plugins
tagDiv speed booster
W3C total cache ( enable only cache page)

Results 72 de 100 desktop
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2F50.97.105.190%2F~cidad259%2F&tab=mobile

URL
http://50.97.105.190/~cidad259/

# BEGIN W3TC Browser Cache
<IfModule mod_deflate.c>
    <IfModule mod_headers.c>
        Header append Vary User-Agent env=!dont-vary
    </IfModule>
        AddOutputFilterByType DEFLATE text/css text/x-

component application/x-javascript application/javascript 

text/javascript text/x-js text/html text/richtext 

image/svg+xml text/plain text/xsd text/xsl text/xml image/x-

icon application/json
    <IfModule mod_mime.c>
        # DEFLATE by extension
        AddOutputFilter DEFLATE js css htm html xml
    </IfModule>
</IfModule>
# END W3TC Browser Cache

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase 

/~cidad259/
RewriteRule ^index\.php$ - [L]
RewriteCond %

{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /~cidad259/index.php [L]
</IfModule>

# END WordPress

accept suggestions?

simchris
tagDiv Member

Hi, Radu
My pleasure to be helpful. I’m not showing up here as a pest, but I do check in just to make sure there isn’t a report of something gone terribly wrong before I update to new version. And, since I live for this stuff every day of the week, and have spent hundreds of hours dealing with WP issues, server issues and optimization this year — I often have two cents to share. 🙂

For the panel, I was actually impressed how you got all those options into the WP built-in panel system. I’ve had tons of issues with other “frameworks” where the framework won’t update, then then the panel breaks, and then the panel isn’t updated, then the panel doesn’t work, etc.

Based on your work so far I have a very high level of “trust” that you’ll do a custom panel the “right way” that won’t break things, or corrupt the DB, or require some arcane framework incompatible with the top 10 plugins.

BTW: we’re moving to a new dedicated server starting on the 20th (hardware being deployed now), so any IP blocks we have in place at the moment will be reset entirely, so if you can’t reach my site, you will be once the migration is completed fully. Retiring our 2008/9 server for more modern hardware.

Keep up the great work.

Chris

Radu
tagDiv Staff

Hello,


@livingsmarttv

Most of your validation errors come from this text widget where you entered html by hand & has to be encoded
http://screencast.com/t/JfrsZRXbp


@MRanki

the errors that we have on our demo are because of the speed booster plugin.. 🙂 See here we have a problem… The validator expects that we put the styles at the beginning of the html in the head section BUT google pagespeed expects it to be at the end of the page. So we went with google pagespeed. Should we get a lower score but validate 100% I do not know yet. Anyway the stock theme does validate HTML5 100%.

  • This reply was modified 12 years by Radu.
Radu
tagDiv Staff

Hello,


@GZAM
– to optimize the delivery of the fonts you can create a colection on google fonts and use a single url to that collection to add them to the page.

The collection url for the default fonts is this: http://www.google.com/fonts#ReviewPlace:refine/Collection:PT+Sans:400,700,400italic|Ubuntu:400,400italic|Open+Sans:400italic,400|Oswald:400,700|Roboto+Condensed:400italic,700italic,400,700

and we via the speed booster plugin we load just one request with all the fonts:
http://screencast.com/t/s2uW3suSDHT instead of 5 (the ensues bellow are used on a default install to allow easy font changing)

After you decide on the fonts you can do a collection of them on google fonts and embed them all in one url.


@GZAM
– do you want to use custom webfonts or web safe fonts?


@Christopher
– we don’t change the jpeg compression quality for compatibility reasons.


@Christopher
we are working on a new panel, new font system and new css generator for the theme. Also we will do most of the templates in the old wordpress way so people can modify it easier. Version 3 will be a major rewrite and I hope people will not kill us for changing so many things 😉

Thanks Christoper for all the comments here on our forums, I really appreciate this and if you have any requests/suggestions or need help feel free to contact me anytime contact@tagdiv.com .

simchris
tagDiv Member

btw, we used font squirrel to repackage open sans to use on our CDN vs loading from Google, and used minified CSS to load the regular, true bold, and true italic versions of fonts, along with the varied font formats for Windows, Mac, iPad, etc.

Brain numbing to do, but worth it if you’re nuts about using custom fonts and speed, and compatibility with stupid IE9/10. Not sure if IE11 has the same issue or not (not rendering italic or true bold Google fonts properly).

simchris
tagDiv Member

I thought Radu or Marius said someplace that better font selection was one of the action items on their custom admin panel, since the current setup is hampered just a little bit by the built-in WP panel they have built options into.

But yes, having option to use web safe fonts would be an excellent option to see in an upcoming version.

Of course always good to remember that Google kind of gives some false positives on
1) fonts
2) adsense
3) recaptcha
4) google+ buttons

they find errors in their own code being loaded on the page; such as image dimensions on ad units missing, CSS for font styles loading off their CDN, recaptcha images needing “more optimization” etc.

A good “goal” for Page Speed right now, based on industry think, is
target desktop = 90 or higher
mobile = 80 or higher

anything below 75 mobile and below 85 desktop would be considered “poor”
but the world won’t crash into the sun if you have a heavily loaded page getting 79 mobile and 89 desktop for the forseeable future, as that is still above the average for 90% of the web.

GZAM
tagDiv Member

another well thought out response – thanks Christopher. If we could have a check box to just use web safe fonts and not use any google fonts, would that not also remove the css loading?

I only see any option to use google fonts, and personally I would prefer to use non-google fonts.

not a huge issue I guess – although it is fairly common for themes to provide the option between web safe vs. google fonts.

cheers…

simchris
tagDiv Member

Just fyi on web fonts …
since the fonts are being loaded from Google’s CDN, there isn’t really any way to “optimize” Google’s loading of those fonts in the way some of you may think – how can the theme optimize something living on Google’s CDN ?. Although “technically” one might remove the &ver=3.71. for some very minor compliance in moving away from that kind of versioning data in WP.

How we did it on our static main business site (not running WP except for news and blog areas, but it’s the same concept in how you might “super optimize” YOUR setup), was we downloaded the equiv fonts (Open Sans family), created style sheet, uploaded both CSS and fonts to our own CDN (S3/CloudFront), setup CORS rules, and now load the fonts off of Amazon’s cloud where we could set expiration times of one year, and compress, etc. In our case we did it both to control all the font parameters for PageSpeed and also the whacky bug in IE for not loading the true italic version of fonts off Google’s CDN without manually inserting calls to all font versions one at a time for IE which results in loading 8 font families per page). Using a custom style sheet to load all the fonts, we load just ONE file for the reg/reg italic, bold/bold italic and solve two issues with Open Sans.

For “most” people you need to setup your compression, and time to live (expiration headers) on YOUR end of things before anything else – that is not a function of the theme. Google how to do that, or contact your hosting provider. Then move on to the other stuff. As GZAM pointed out, and as I have previously, the compression and expiration headers alone account for about 20 points or more in Google Page Speed.

Fonts are a tricky bit, where any “designer” fonts, slow down page regardless, as they have to be loaded from somewhere. For those looking for “fastest speed” once everything else is done, you might have to NOT use custom fonts at all, and sub out Trebuchet MS for the menus, and something like Georgia or Arial/Helvetica for the body text.

Spending the $2 a month for Amazon’s CDN (or similar) is one way to speed up your fonts, vs loading them from Google directly, but that is something you need to try, modify, test, modify, test. For example, we use Font Awesome, and we tested loading that off the cloudflare hosted version vs our CDN on Amazon – Amazon was faster so we load that from there.

Not sure if any of that helps. It is a process, not a one click thing to optimize a page for ‘speed’ — there is NO “one click” solution out there due to complexity of servers, content, and everything being loaded on the page.

For example on optimization — if you want faster speed, what about image compression level using built in functions of wordpress? Did you know you can use a plugin or function to increase the compression level of the thumbnails appearing on the pages? Smaller files there make page load faster even before server side gzp/deflate. These are the kinds of things you need to research if trying to optimize your site for fasted load times.

For example, you could set the compression of images to something like 60% or even 50% in your child theme functions.php … will only change level on new images uploaded unless you use the regenerate thumbnails plugin or similar.

add_filter( 'jpeg_quality', create_function( '', 'return 50;' ) );

I’m not sure what Radu has the quality set to by default, but increasing the compression even 10% from the default improves speed.

Additional ref:

switch ( $mime_type ) {
 case ‘image/jpeg’:
return imagejpeg( $image, $filename, apply_filters( ‘jpeg_quality’, 90, ‘edit_image’ ) );
case ‘image/png’:
return imagepng( $image, $filename );
 case ‘image/gif’:
return imagegif( $image, $filename );
 default:
 return false;
 }

Google’s webpagetest.org actually recommends quality level 50 for web images.

We are shooting for “60” at the moment (60/100 compression is not percentage of compression, btw).

  • This reply was modified 12 years by simchris.
  • This reply was modified 12 years by simchris.
  • This reply was modified 12 years by simchris.
Viewing 25 results - 2,976 through 3,000 (of 3,025 total)