Google's PageSpeed Insights tool can certainly be very helpful but it is also useful to remember that the results are just Google's ideal recommendations (without any knowledge of the content of the page or if any of their recommendations can even be implemented).

With regard to the 'render-blocking JavaScript and CSS' message, the results note:

That is correct but, knowing the content of your web page (the only content above-the-fold is your Juicebox gallery), it is absolutely necessary to wait for the 'juicebox.js' and 'theme.css' files to load before the gallery can be displayed and is visible.

The 'Prioritize visible content' message notes:

That, again, is true. Additional resources (the gallery's 'config.xml' file and the JavaScript, CSS, image and font files in the 'jbcore' folder) are required due to the design and required structure of Juicebox. However, there is nothing that can be done to incorporate all these resources directly into the gallery's HTML embedding page and the message is really nothing to worry about.

Knowing the way that Juicebox works (requiring the 'juicebox.js' and 'theme.css' files to be fully loaded before the gallery can be displayed and also requiring an external XML file and the 'jbcore' folder) the two warnings above can be put into context. They are not truly problems but necessities for the gallery to be displayed and function correctly.

Try entering other popular websites (such as 'http://google.com' or 'http://amazon.com') into Google's own PageSpeed Insights tool and you'll see that the results are often similar to those reported for your own Juicebox gallery web page.

When using any library or package which requires a number of external resource files (such as Juicebox and its 'jbcore' folder), you'll find that the PageSpeed Insights tool gives similar results.

You could certainly set HTTP cache headers within an .htaccess file if you like. Try a web search with terms such as 'http cache header htaccess' to find out more information.
However, such a decision (to force browser caching or not) is really up to the individual user (and not directly Juicebox dependent).

Incidentally, all these messages refer to the Speed section. The User Experience section for your Juicebox gallery page gives a score of 100/100 with the message "Congratulations! No issues found.".

I hope this helps to clarify things.

Out of interest, I've just loaded a Juicebox-Pro v1.4.1 gallery into an iframe and the Expand Button seems to be disabled in this version (just like in v1.5.0).

The Expand Button is disabled by design when the gallery is loaded into an iframe to avoid a lot of potential problems.

There are several things to consider such as the values of useFullscreenExpand and expandInNewPage and the browsers and devices being used to display the gallery. (Please see the Expand Gallery Behavior for some more information. Expanding a gallery can be quite complicated!)

Also, not all users will be using up-to-date browsers which support the Fullscreen API (perhaps in corporate environments).
Juicebox supports IE 7 and later so we need to be sure that our user base will not encounter any unexpected or unusual behavior in older browsers. IE 7 is certainly a bit long in the tooth now but the Fullscreen API was first supported by IE in version 11 and there seems to be more than a few people still using IE 8, IE 9 and IE 10 (over 10% of the total browser market share).

I would normally recommend that you use the current version of Juicebox-Pro but if you find that Juicebox-Pro v1.4.1 works for you and you are not affected by any bugs which have since been fixed in subsequent versions, then you are certainly free to continue using v1.4.1.

I'm not sure how relevant this is to Juicebox but I appreciate you taking the time to point this out and I have notified the developers of your post above. Thank you.

It is true that metadata is not retained when JuiceboxBuilder resizes images but the loss of metadata is happening within a desktop application on the user's computer (rather than via the upload functionality of an online service) and then the files are being uploaded to the user's own web space. (We do not host any user galleries or sites at all.) I guess it's not for me to say how similar (or different) the two scenarios are.

Incidentally, I've just uploaded a test image (with EXIF and IPTC data) to a Showkase v1.6.1 site's Library and the image's metadata was retained after Showkase had resized the image. It looks like issue affects only JuiceboxBuilder.

As I mentioned earlier, it's not that JuiceboxBuilder is intentionally going out of its way to strip metadata from images, it's just that when an image is resized, the metadata would have to be read and stored somewhere before resizing and then written back to the new image after resizing. I do not know if the Adobe AIR API (which JuiceboxBuilder uses) has any methods available that could be used to make this possible. (I expect there would need to be different metadata read and write functions for different file types.)

I realise that, from a user's perspective, the issue is simply that metadata is not retained and the reason why this happens is not important but giving a little background information may at least help in understanding the problem.

Adobe seem to have been slow in implementing this in Muse (see this forum thread) and I do not know if AIR applications are still lagging behind. However, I'm sure the developers will investigate further.

Thanks, again.

It seems strange that this error message would appear in only certain browsers (but not others).
I would expect such a problem to affect all browsers (or none).

Try clearing your Safari browser's cache before reloading your gallery's web page to see if this helps.
Also, if you have any extensions installed in your Safari browser, try temporarily disabling them to see if this makes a difference.

If you continue to experience difficulties, please post the URL to your gallery's web page so that I can take a look at the problem for myself and hopefully help further.

In the meantime, maybe this FAQ will help:
When I view my gallery I see the message 'Config file not found'. How do I fix this?

When you upload images via the WordPress media window, the images in your WP-Juicebox gallery should initially be in the order in which they finished uploading.

To sort images after a gallery has been created:
(1) 'Edit' the post containing the gallery
(2) Click the 'Add Media' button
(3) Select the 'Insert Media -> Media LIbrary' section (selected by default)
(4) Choose 'Uploaded to this post' from the drop-down menu
(5) Drag and drop the images into your chosen order
(6) Close the 'Add Media' window

You may need to clear your browser's cache after reloading the gallery.

If the images initially look like they are in the right order in the media window but do not appear in this order in your WP-Juicebox gallery, just drag and drop a thumbnail into a new position and then drag it back. That should be all that is required to change the order from the 'finished uploading' order to the visible 'menu' order.

You're welcome!

Thank you.

The problem certainly seems to be the space in the path.
I have been able to replicate the problem using a gallery folder name containing a space.
(The Download Button works fine in the same gallery when there is no space in the path.)

One possible solution seems to be to decode the '%20' back to a ' ' in the $fileUrl variable.
Try changing line 6 of the 'juicebox.php' file from:

... to:

I'm not sure that this is the best solution but it should hopefully work.
I have notified the developers of this problem.

Please note that the line number above refers to the current version of Juicebox-Pro (v1.5.0).

The best solution would be to not use spaces in paths.
As image filenames and gallery folder names form parts of URLs when uploaded to a web server, it would be safer to use only web-safe characters. Please see section 2.3 of this document for details: https://tools.ietf.org/html/rfc3986#section-2.3

You should have no problems (with JuiceboxBuilder-Pro, your web server, FTP software or browsers) when using any or all of these unreserved characters.
(The space character is considered 'unsafe' as it needs to be encoded.)

It looks like the following custom CSS from your 'fsa_theme.css' file may be causing the problem.

/* To hide Juicebox logo */
.jb-classifier-link-wrapper + div{
    opacity: 0;
    visibility: hidden;
}

As you are using Juicebox-Pro, the Juicebox logo will not be displayed in any of your Pro galleries so this custom CSS should not be required.

I hope this points you in the right direction.

Incidentally, Juicebox (both Lite and Pro) may be used for personal and/or commercial projects but, if using Juicebox-Lite, please ensure that the Juicebox download link in the bottom right corner is clearly visible. Thank you.

@fkelly12054

Thanks for helping out.
As you say, all that is required to have a different audio track per gallery is to supply an MP3 and an OGG file for each gallery and set the appropriate audioUrlMp3 and audioUrlOgg paths in each gallery's XML configuration file.

Just in case it helps, there's a link to an online converter in the Adding Audio support section.

In order to set configuration options (such as flickrTags) via a query string in the URL, you'll need to set debugMode="TRUE" in the gallery's embedding code. (Please see the Setting Config Options support section for details.)

To do this within the Juicebox plugin for WordPress, open WP-Juicebox's 'wp-juicebox.php' file in a plain text editor and change line 280 from:

$string_builder .= '        backgroundColor: "' . $background_color . '",' . PHP_EOL;

... to:

$string_builder .= '        debugMode: "TRUE", backgroundColor: "' . $background_color . '",' . PHP_EOL;

You can then set a flickrUserName via the WP-Juicebox gallery settings interface (as usual) and set the flickrTags option via a query string in the URL, for example:
http://www.example.com/gallery/?flickrTags=landscape

If you wanted to, you could set the flickrUserName (or any other configuration options) via the query string, too. Configuration options set via the query string take precedence over those set via the embedding code or in the gallery's XML configuration file. For example:
http://www.example.com/gallery/?flickrUserName=my_flickr_account&flickrTags=landscape

Please note that the line number above refers to the current version of WP-Juicebox (v1.5.0).
(In the version of WP-Juicebox that you are currently using, the line to modify will be somewhere in the region of 289 ~ 290.)

Please fill in the Download Link Request Form and the admin team will send you a new download link.
Just fill in the form to the best of your ability (with an approximate purchase date if you cannot remember the exact date) and use the 'Additional Information' box at the foot of the form to add any notes which might help the admin team find your transaction details.
Download Link Request Form: https://juicebox.net/admin/download_request/