Search Results for 'pagespeed'

This is common with all wordpress themes (and most websites really)… it’s not an issue with this theme.

If you’re interested in “some” of the tricks we’ve been using to try to get around this check out the pagespeed sticky topic.

Using the tagdiv speed booster plugin can help, as can things like caching, mod_pagespeed with hosting provider, etc. It basically “enqueues” several things to load better on pageload.

https://forum.tagdiv.com/topic/pagespeed/

It’s a process, I can tell you. I also wouldn’t stress over it tooooo much. Worry about everything ELSE first, and leave THAT for last. Note some of the blocking errors will come from Google’s own products like AdSense.

• This reply was modified 12 years by simchris.

Hi,
I think a VPS would be overkill unless you are making a living from your blog or intend to host multiple blogs and want “total control” of your environment. Nice to have “room” to try different themes, sites, domains, etc., without having to sign up for a “domain based” account someplace. If you do choose a host, look for one that supports mod_pagespeed and also knows what wordpress is 😉

For a CDN, likely not needed unless the host is terribly slow (for example, a slow $5/month hosting plan plus $1/month CDN can be cheaper than $10/month plan, in theory).

For us, a CDN is useful as folks in NY or Canada can get stuff loaded faster when we’re in Calif., and servers are in Texas. It does seem to help as the CSS/JS/images all load from closest “edge” location. Again, usually more necessary for a business case than a blog case (my magazine sites don’t make any money really; they’re a bit of a hobby side thing from our main company business which does rely on high “availability” hence the fun I am personally having right now optimizing shtml/ssi pages in one place and WordPress everywhere else … each need different tweaks… ).

Obviously a host with “point of presence” in Norway is best choice. You don’t want to be loading pages from Texas when your audience is in Norway. I have not used BlueHost. We use SoftLayer to have a full server here in U.S., but that’s totally different from what you need.

Hey!
I chose to use Amazon’s CloudFront since I already have Amazon account and they bill my card on file (I think December was $0.98). CloudFront works well, aside from this pesky issue with Font Awesome 4, which I’m getting same issue from boostrapCDN (free) — sometimes the icons won’t load in IE10/11 or Firefox (both on Windows) for no good reason.

Anywayyyyyy….. in my case I’m using S3+CloudFront since my brother’s company (in the educational software business) uses it, a lot of folks have been testing running WP sites virtually entirely in their cloud (!), and I’ve got a nice app called Cloudberry S3 Explorer which works as both bulk FTP, header settings for expirations, ACL/Public settings, and CloudFront invalidations. So, it was just kind of the best choice. Right now only loading CSS, JS, fonts, static images (logos, little things like BBB bug, etc.). Not yet using for WP.

Upshot … I think folks would likely spend the 30-cents vs free to “test” both for speed.

In my case I did test couple of things against CloudFlare and where I’m at there was couple of msec saved, so seemed worth it to just use Amazon since I know they’re not going to disappear, or get bought by Google and squashed or anything else with other cloud stuff might throw out there. I’m also inherently suspicious of anything “free” as that is no business model, and I need reliable here today, here tomorrow setup for our main business site. So, $1 a month to count on it, vs “free” and might be gone without warning. Was easy choice for me.

Haven’t yet done anything with the WP stuff as waiting for Newspaper “3” if it will have classic WP ‘header.php’ file where I can just point a bunch of the CSS/JS stuff at the CDN without hacking something that will then need re-hacking in 2 weeks.

I also did some research on some articles around and since I don’t need SSL off the cloud (after all I have my own damn server!), this was food for thought:
http://robin.userapp.io/post/66094840975/finding-the-right-cdn-for-our-startup-maxcdn

Varnish does wonders! I can vouch for it as I have it on my server and it truly pays off.

@christopher

Do you know what the advantage of using a CDN like Amazon over CloudFlare is? I’m only using CloudFlare, and for a free service it’s insane how much it does. Not to mention that if your server goes offline, visitors can still access cached pages.

Here’s the link to the specifics of the speed achieved by Radu and Co. for theme (keep in mind this is with no AdSense or certain funky Facebook boxes which lower scores due to issues with the code being injected, and not issue with the theme):

(OFFICIAL)
https://forum.tagdiv.com/how-to-make-the-site-faster/

Once you do that, then you may want to look at all the shared posts in the pagespeed topic, specifically my shared elements to put in your .htaccess file, if not there already.

• This reply was modified 12 years by simchris.

FOR FIRST TIMERS SEEKING TO SPEED UP SITE.
you may find this useful, if you’re going to test using W3 Cache as part of your page speed strategy:

http://gtmetrix.com/wordpress-optimization-guide.html

@Octavian
nice!!

I’ve been sidetracked the past week trying to sort out the random issues with Amazon’s CDN where randomly the font awesome CSS won’t load in IE11 or Firefox on Windows, leaving unstyled elements on our business site; and now the background for one sub-head divider won’t load the background image when using either ../assets/img/filename.gif or the full explicit URL in style sheet. Makes no sense. Went back to loading the FA2 fonts from our own server. Sigh. (This applies to our business site, not the magazine sites; the business site doesn’t use WP for main content, so a bit more flexible; pages are static to begin with so full page caching not needed, obviously.)

As to the WordPress stuff… we’re not using a true “page cache” yet, just the mod_pagespeed caching of page “elements” and not yet using a CDN for the CSS/JS. But this page is not bad; testing a typical article page sans a YouTube video or the AdSense elements but with AddThis in place to see how at least one “pagespeed stumbler” impacts ratings.
http://gtmetrix.com/reports/ga-ga.com/IyjAjIea

GPS: 97 (“A”) / YSLOW 90 (“A”)
Page load time: 1.29s
Total page size: 425KB
Total number of requests: 41

So, 1.29 seconds without page cache or CDN is pretty much not bad as starting point for us, which I could live with before the “next level.”

I’m not yet doing anything further until the new version of the theme drops from Radu’s magic labs.

Apparently for our WP sites, we’ll likely end up using “Varnish” on the server, to manage static pages locally, in front of mod_pagespeed, which peeps tell me is “how it’s done.” That is what is going to get the pages loading in the sub-second range. I may retry the caching plugins for WP to save local copies as I think mod_pagespeed can rewrite the pre-cache or post-cache copy, but still unclear on that. Not sure what Varnish will do to our ecom system or other stuff, so having enough fun with one thing before suffering another.

Great job on the speed!!! 🙂 YOWZZA!

• This reply was modified 12 years by simchris.

It actually loads faster than my other site with no CMS and 33% of the page size! http://screencast.com/t/f9rxWNJrfw0

Yeah baby… You first saw it here 🙂

Server is in NYC http://screencast.com/t/lEPSesG5frE

Hi, Radu
that would be awesome. I switched from using the child theme so as to not impact my pagespeed adventures, and so the custom CSS I put at bottom of style.css didn’t have an impact in the way the child/style.css did. Being able to tweak a few things here or there with either a custom.css file, or perhaps more appropriately these days a “hook” to drop some code in the head at bottom before the body tag (Woo Themes does this fairly well, btw; they have all these little ‘hook’ locations to drop in code, although it does add a slew of if/then crap; disclosure we’re trying to ramp up your theme to replace Woo Canvas!).

So for us to be semi-done and in full “go mode” my laundry list of stuff needed is simply:
1) Google async alignment in top bar
2) websafe fonts option – which would save me hacking that one
3) custom.css injection hook in head, to over-ride couple of minor things (like making the author box bio text size smaller, when making the post side larger so the author bio isn’t over-large from the base adjustment)
4) not critical; but option to have a local image for author box (add new user meta field for ‘author image’ — we used to do this on our in house theme, not difficult) to not pull gravatar and save some bandwidth from external site — if you wanted to wow the kids, you could add a “grab my image from gravatar” option 😉 Peeps love the “automagical” stuff.

Otherwise, for us — you’re done! I’m hoping the v3 won’t introduce new issues, but right now we’re very happy.

BTW: for ‘web safe’ fonts, Adobe came up with some really quite brilliant ‘stacks’ of the best font mix to use across Mac, Windows, iOS, Android, et al. They can be found in Dreamweaver, and possibly their help system – but if you need those, just let me know. Much nicer than the old skool ‘Helvetica, arial, sans-serif’ stack. 🙂

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

Zeus…
I also updated my expiration headers (see the pagespeed thread sticky top of forum) for htaccess to add more time for .js files due to the wordpress comments js file normally expiring in less than one week. I had it set at 2.6 days; Google now wants a week and will generate error on pagespeed insights for that one pesky file!

Hi, Anna
we’re running the latest “stable” release from November. The current January version is an “edge” (or “Beta”) which is on different development track. So, hoping the stable version will be updated end of January with some of the new fixes.

Since our main sites are mission critical we dialed back all the filters server wide to just the CoreFilters minus one lazy load element (have an over-ride to lazy load images on page load and not on scroll as that did weird things).

Originally tested with a “full set of best choices for WordPress” but we’d see that something caused conflicts and so doing side by side speed of loading tests, most of the time the pages would load more quickly with mod_pagespeed OFF, which didn’t make much sense.

Now, I’m testing the filters sort of case by case, then testing the “mix” of elements (e.g., fonts, adsense, grvatar, addthis/social buttons) with each option, trying to use as few as possible to not actually slow things down (meaning why have mod_pagespeed do something which doesn’t actually need to be done — 10 extra filters adds some latency somewhere, although if done pre-cache not a biggie “in theory”).

It’s also worth noting I hacked the addthis plugin to add the “async” method which is not built-in (stupidly); which can be found in one of my other posts.

The adventure continues on Saturday!

Also note that some “master filter” settings enable sub filters, as so:

ModPagespeedEnableFilters rewrite_images (apache)
in the configuration file. This is equivalent to enabling
inline_images, recompress_images, convert_png_to_jpeg, and resize_images.

And then recompress_images is a master ‘group’ filter set for the following:
This is also a group filter, and is equivalent to enabling: convert_gif_to_png, convert_jpeg_to_progressive, jpeg_subsampling, recompress_jpeg, recompress_png, recompress_webp, strip_image_color_profile, and strip_image_meta_data.

So as you can see there are
master group >> sub master group >> end filters part of sub-master group

hence the phrase “tricky” 🙂

I am testing the master groups first to find what doesn’t work; then sub-groups, then down to specialized sub-filter settings.

• This reply was modified 12 years by simchris.

hello,
what type of hosting do you use?
try to stay away from really cheap ones.
there is a thread where users have posted solutions for speed increase
https://forum.tagdiv.com/search/pagespeed/

Thanks for you message.
Radu A.

Hello Chris,

nice tips and informations, thank you.

What version of mod_pagespeed are you using?

Did you tried one the last filters, “Deduplicate inline images”?

It seems really interesting:

https://developers.google.com/speed/pagespeed/module/filter-dedup-inlined-images

Thanks

Ooops: one more.

For those who are testing for speed-speed-speed and want to fix all their “you could optimize image xyz” warnings. I actually wrote an article on this once upon a time on my old site no longer seen anywhere since it was behind a login.

BASICALLY:
1) backup all your images
2) install the wp regenerate thumbnails plugin
3) check your wp settings > media and make sure the S / M /L sizes match what is being used by theme so you don’t end up with more thumbs than needed (seriously this is the #1 mistake folks make with thumbnails in general)
4) add the following code to your functions.php file in the theme root at the end –or– in your child theme (TIP: stop using a child theme)
add_filter( 'jpeg_quality', create_function( '', 'return 50;' ) );
5) run the regenerate thumbnails plugin under wp admin > tools

Voila!~ go rerun your speed test with Google and magically no more “you need to optimize image xyz to save 5kb” crap.

If your images don’t look as sparkly as they did, you can always delete the thumbs, put your original images back, and then try changing the “50” to “60” if you prefer.

For all those thumbnails all over the place “50” is recommended setting, and this uses both the built-in function of wordpress for images which hooks into the image mod stuff on the server. UPSHOT: when you make this change to your functions.php file – ALL YOUR FUTURE IMAGE THUMBS will be compressed automatically.

No more extra plugin to do that unless you really want to.
Simple. Easy. Quick.

Pagespeed mod test update: settings 0.4

Google Pagespeed 93/100 on main GPS Insight
page: http://ga-ga.com/1262/fiction-area-code-666-part-18-del-arton/
– google adsense – no ads for test
– addthis plugin replace social media buttons with single button ‘on’
– gravatar loaded dynamic over network for author box

todo:
1) load author image locally either with plugin, or add field to functions.php to add new user datafield, then call user meta for the field instead of gravatar code.
2) reduce server response time — typical is 0.32 seconds (320msec) up to 4 seconds; but Google now saying <200msec is the “ideal” — not sure tradeoff on optimizations for everything else; but I did see a post the other day about server tweaks to speed up “first byte” load of WordPress pages to deal with that so called “error.” Solving this would negate the penalize from Google AdSense being on.
3) super annoying “reder blocking” CSS almost “quashed” and ironically the error is from mod_pagespeed trying to fix:

Optimize CSS Delivery of the following:http://ga-ga.com/…ootstrap.css.pagespeed.cf.n0P3fhMJJz.css
http://ga-ga.com/…/A.style.css.pagespeed.cf.JAYrGYtjNo.css

– so in typical GPS fashion, one Google product complains about another Google product which is designed to fix the complaint in first place (ARGH!). This one will take some playing around with the “filters” which is where I got stuck this past weekend.

Hope this is entertaining somebody 🙂

and I forgot to mention here is the code I’m using in my htaccess file for mod_pagespeed testing, in addition to CoreFilters being on from the main .conf file at server level, eventually this would be a <directory> directive in the .conf and not in htaccess for better optimization.

<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters move_css_to_head
ModPagespeedEnableFilters combine_css
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>

CHANGE to my prior htaccess code for expire headers to solve one javascript file for comments in the core wp code:

AddType text/javascript .js

# BEGIN Expire headers
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 5 seconds"
ExpiresByType image/x-icon "access plus 2500000 seconds"
ExpiresByType image/jpeg "access plus 2500000 seconds"
ExpiresByType image/png "access plus 2500000 seconds"
ExpiresByType image/gif "access plus 2500000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2500000 seconds"
ExpiresByType text/css "access plus 700000 seconds"
ExpiresByType text/javascript "access plus 700000 seconds"
ExpiresByType application/javascript "access plus 700000 seconds"
ExpiresByType application/x-javascript "access plus 700000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</IfModule>

I also added these to the end of the htaccess after the cache control headers, to solve the ETag problem and also the damn spammers hitting my ping script.

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

AS EVER: do not make changes to any of your files/settings unless you have backups done.
THis is all experimental at this point; when I have a solid Apache-friendly setup, I will share all the settings in all the files for those interested in this discussion. 🙂

Cheers,
Christopher Simmons
member: PRSA, ASCAP
CEO, Neotrope®
Torrance, CA, USA
(please don’t call me asking for help on anything at this point in time; I will resume my consulting biz once I have my own ducks back in a row, as it were!)

• This reply was modified 12 years by simchris.

OH:
in case anybody is curious about my misadventures in

JANUARY TWEAK FEST
– tagdiv speed booster to enqueue stuff
– google font calls removed from functions.php; style.css mod to change default fonts to:
font-family:Segoe,"Segoe UI","DejaVu Sans","Trebuchet MS",Verdana,sans-serif
– mod_pagespeed corefilters on, layz load images off until page load
– manual mod_pagespeed “switch on” via htaccess to test impact
– optimizations in htaccess (remove “collisions” for typical mod-deflate call, taken care of by mod_pagespeed)
– optimizations in wp-config.php
– optimizations in functions.php

using GTNetrix for the testing right now
(6pm PST 1/16/14)
http://gtmetrix.com/reports/ga-ga.com/MJRvlvaL

TESTING THIS PAGE:
http://ga-ga.com/518/discwatcher-blu-ray-movie-review-prince-of-persia-the-sands-of-time/

mix of images, thumbs, youtube video, addthis social button, aysnc google ad

GTMETRIX ENGINE SCORE with my “0.03 settings” I’m up to tonight
98/PS and 82/YSLOW
Page load time: 2.30s
Total page size: 1.02MB
Total number of requests: 53

I AM NOT USING ANY WP CACHING PLUGIN, NOT USING ANY MINIFICATION PLUGIN; beyond mod_pagespeed and server side functions for these tests.

With the main Google PageSpeed Insights page,
score is: 89/100 desktop and 77/100 mobile

Oddly for current Google main speed testing, turning ads off completely along with turning author box off to remove gravatar pull, also didn’t actually increase initial rank. Nor did turning off the addthis button. More testing underway!

A page without youtube video, with addthis on, google advert off, author box on for live gravatar ( http://ga-ga.com/492/growing-older-in-a-youth-oriented-society/ ) ; pagespeed 91/100 desktop and big jump for mobile to 83/100. YouTube really is a suck for the PS rank.

Some our sites generate 2+ million page views per month and have been online 14 years with 230,000 inbound sites for pagerank. We have been managing our own servers since 1996, and ran a hosting company from 1996-2005. We did Oprah Winfrey’s ecom solution for her “Begin with Love” videos a decade ago. Pretty savvy. We are also PCI-DSS certified, and have weathered serious server attacks so have complex security stuff in place. ‘=)

We do use nginx along with Apache 2.2 – for instance phpmyadmin runs on nginx. 32GB of RAM, dedicated 1GB switch at SoftLayer in Texas. Power to burn. Replaced our 2008 server with 12GB RAM and 8 cores. Wild times compared to the days of, say Cobalt RaQ4 (google it).

Still playing with mod_pagespeed stuff as they have lots of cool things like “inline_google_font_css” (Inlines small CSS files used by fonts.googleapis.com into the HTML document.) which I’ve not yet been able to get working. Defer javasceript is another one built-in which is cool.

Stable version from November, edge version from January, and you can’t mix ’em.

Anyway… I’m trying to find the balance of the traditional hacks
1) mods to the wp-config.php
2) mods to functions.php
3) mods to htaccess (Apache)
4) manual optimization of css file if a rewrite system breaks it
5) upload best practice optimized images to begin with; generate smaller thumbs to start with using built-in compression of WordPress vs plugin for initial files; remove duplicate sizes in media setup to match theme size

6) use mod_pagespeed to manage cache (with memcache, eAccelerator, APC, etc.); rewrite on the fly to cache copies with comments removed, delete white space (instant minification!); combine CSS, combine JS, etc.

6) when all that fails to keep a “92” dump the CSS/JS onto the CDN, keep images local.

This is my mission for January. Once done, I’ll have a better sense of what actually works and what is truly a fool’s errand.

BTW: my friends at GTMetrix have a nice plugin for WordPress for testing/tracking pagespeed adventures (recommended!).

MOre later in the pagespeed “forum” here 🙂

I will probably end up doing some kind of ebook for this whole shenanigans.

Chris

• This reply was modified 12 years by simchris.

We own our own server, so we’re running mod_pagespeed on Plesk[ne Parallels]11/CentOS6.5 in order to solve some things across different types of content sites (not all WordPress). Being able to defer javascript with WP is helpful. Being able to recompress images at server level, combine small PNGs to sprites, etc. mean we don’t have to use Smush.it, EWWWW, etc. for most things. Using the built-in WordPress compression level function to make thumnbails generate at “50” vs “80” also a big help before anything else is done. Idea is trying to run stuff at server level above the PHP stuff where possible vs having plugins being called as each page renders. Nice thing with mod_pagespeed is also inserted image dimensions for “responsive” images for faster page render. E.g., on one of our sites the images are 400×300, but render on page at 70% of the column “width” via CSS — mod_pagespeed will actually rewrite the actual size on page (e.g., 431xNNN) for faster page load. Some really interesting stuff. We run memcache and are storing cached elements in RAM and on the disk, before the page write – so, in theory, this is a level above using a cache “plugin” in some ways (although end result is same probably).

Still testing 🙂 Just got a good working version across all sites as of Tues. night (two days ago). 10 days of “try this, nope. try that, nope. WTf? Oh! What? Hey! Oh. Okay…” … 😉

Seems like you should already be able to minify the .css for the main style sheet if you know all that stuff ! Kind of surprised Super Cache isn’t able to minify.

But sounds like you’re an above average user, so likely you’ll be able to come up with a solution for the CSS minification if you don’t want to do it manually.

I’m suffering an 82/100 desktop at the moment due to addthis, google syndication/adsense, and youtube video on a page. 92+ with that noise off and no cache plugin (!).

We stripped out the Google font calls entirely, and did search/replace in style.css for default fonts. Got rid of the stupid Google insights “error” for their own stupid fonts.

It’s a process. Since we have a shiny new 12 core Xeon server, been trying to get this tweaked to do as much as possible at top. Considering adding Varnish, but another pain in the butt to sort out. Day 16 of the “how much can the server do to fix stuff on the fly” adventure. Would be nice if Google fixed their own crap for Insights to at least give a reasonable speed grade taking into account THEIR problems.

No magic bullet. Funny how some “experts” who claim 100 pagespeed are running sites with plain text, no graphics and one ad on page, and then try to give advice for those running newspaper/magazine sites which by nature are very complex.

Thanks Christopher. I took a look at mod_pagespeed, but it doesnt look like it could do anything for me at this point. I’m already on a VPS that runs Plesk 11 with nginx as a reverse proxy. I’m letting nginx handle all php scripts and serve static and dynamic content. Gzip compression is enabled and i enabled browser caching through nginx with the expiration set to two weeks. I’m running WP Super Cache as well to create pre cached pages and i use EWWWW Image Optimizer to optimize all images. I also optimazed all theme and plugin images with that plugin. You might want to look it up, imo it really is a better plugin than smush.it and so. I use the simple minify plugin to minify all javascripts and i my pagespeed currently toggles between 85 en 92 for desktop, depending on my server response time and between 70 and 80 for mobile. The only red warning i still get is to defer javascript and css (moste google fonts, and 3 theme css files: bootstrap, style.css and child theme style.css) to below the fold, but i have no experience on how to do that. Im really pleased with the pagespeed right now, but more tips (besides using a CDN) are welcome!

Thanks for you responce anyway 🙂

Note to all, we found it’s better to manually minify the main style.css file each update.

HERE IS HOW TO:

The easy way to minify your main style.css file, is to
1) in your theme folder, make a copy of the style.css file (rename style-bak.css or whatever)
2) take the style.css file and open in a text editor (NOT a word processor), like Notepad or TextPad on Windows, or similar.
3) copy and paste all the text from the file into a minifcation online tool like one of these:
– http://refresh-sf.com/yui/
– http://cssminifier.com/
4) copy the “minified” output into a new style.css file
5) upload via FTP to over-write the style.css file in your theme root

Now when you run PageSpeed Insights it won’t bug you anymore. I do this and works just fine.

r1kay
to clarify, mod_pagespeed is not a WordPress plugin, but is used at the server level and is being used by many “speed oriented” web hosting providers now, including many that specialize in WP hosting specifically (and larger folk like GoDaddy, etc.).

The easy way to minify your main style.css file, is to
1) in your theme folder, make a copy of the style.css file (rename style-bak.css or whatever)
2) take the style.css file and open in a text editor (NOT a word processor), like Notepad or TextPad on Windows, or similar.
3) copy and paste all the text from the file into a minifcation online tool like one of these:
– http://refresh-sf.com/yui/
– http://cssminifier.com/
4) copy the “minified” output into a new style.css file
5) upload via FTP to over-write the style.css file in your theme root

Now when you run PageSpeed Insights it won’t bug you anymore. I do this and works just fine.

If none of that is remotely possible for you to do, then don’t stress over it. You only gain maybe a point for doing this, along with a couple of other things. Image optimization is far more important, and limiting use of plugins which “dial out” from your site to load things on the page beyond your content (social media “counters” for instance – plain buttons load faster).

You likely haven’t seen mention of mod_pagespeed as you have not been looking through the “pinned” topic at top of forum on “Pagespeed” issues.

Note when minifying the css file, it will save 20% of the space, but it doesn’t speed anything up by 20% or improve rating by 20%. If it saves more than 20kb then it’s worth it. If it saves less than 20kb may not be worth the trouble.

ALSO: be aware each time you update theme you will need to re-compress the style sheet using one of the tools above.

Hope that helped.