Master page publish .html and .css

[benkn]

I am updating an older WB site.

When I built the site 7 years ago, I used master pages.
When i published, i could "explore" my site in the built in FTP. I would see page.html ONLY.

Now, in my updated site, I see page.html AND page .css (for ALL pages that use a master page)

Does this mean shared images will need to be reloaded when users go to a new page?

What is different than 7 years ago?

Note: I didnt use a content place holder in my previous, older version.

I've read the support tutorials on the three types of master page: 'embedded page' might be what I am looking for, what I used 7 years ago, but it's a big site and i want to make sure first before I do it many times.

[Pablo]

If you update the master page, then all pages that use this master page must be republished.

Note that you can control the output format (HTML, CSS, JS) in Tools -> Options -> HTML

[benkn]

What I am doing is deleting the old page, then, then publishing ("selected page ONLY", "all files") my new page.

What is happening after i click publish; two pages are being published, one page.html and one page.css.

It looks correct. its somehow publishing the master page i think.

It looks correct, im just wondering the best way to control the load speed, as my users go to multiple pages.

[Pablo]

What is the exact problem?
What would you like to change?

[alan_sh]

What I am doing is deleting the old page, then, then publishing ("selected page ONLY", "all files") my new page.

What is happening after i click publish; two pages are being published, one page.html and one page.css.

It looks correct. its somehow publishing the master page i think.

It looks correct, im just wondering the best way to control the load speed, as my users go to multiple pages.

It's not publishing the master page - that gets 'embedded' in your "real" page when it comes time to publish. The later versions of WWB publish a .css and a .html for every page you publish unless you tell it not to.

Try publishing the whole site with the new WWB (do it to a local folder if you don't want to overwrite your web site) and you will see lots of .css files.

Alan

[benkn]

Thank you Alan and Pablo,

Here is my concern:
Below is from a speed test (https://pagespeed.web.dev). (bookmark that test btw, pretty cool)

Right now, I'm trying to determine the best way to build; which type of master page; embedded or not.

These speed tests seems to be recommending embedding. I guess I am weighing the immense amount of rework to go with embedded pages.

I have been using a master_page (added though page properties/misc.). This seems to be working well, and performing as I expected.

My users all go to many pages. ******* Im wondering if they need to reload my logo, nav bars, and repeated images every time they go to a new page, and what will be the case if I go with "embedded" instead of master page. Which method will create the best user experience? ********

Note: "untitled1.css" (below) appears to be font information and such. No clue how it got published.
Note: below is TWO separate suggestion from the speed website (that seem to say the same thing.

------------------------------------------------------------------------------

Eliminate render-blocking resources
0.29 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
/Untitled1.css(www.usedgondolashelving.com)
0.6 KiB
180 ms
/liquidation_services.css(www.usedgondolashelving.com)
7.5 KiB
330 ms

--------------------------------------------------------

Avoid chaining critical requests 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.FCPLCP
Maximum critical path latency: 440 ms
Initial Navigation
/liquidation_services.html(www.usedgondolashelving.com)
/Untitled1.css(www.usedgondolashelving.com) - 180 ms, 0.63 KiB
/liquidation_services.css(www.usedgondolashelving.com) - 270 ms, 7.52 KiB
/Untitled1.css(www.usedgondolashelving.com) - 180 ms, 0.63 KiB
/liquidation_services.css(www.usedgondolashelving.com) - 270 ms, 7.52 KiB

[alan_sh]

I would have thought that browser side caching will take care of any potential reloads. I don't use 'embedded' myself, but if you want to look at one of my sites (e.g. penninescouts.org.uk), the header, menu and logo are all in my master page. See how it 'feels' for speed when you move pages.

It may be that you have a solution looking for a problem.

Alan

[crispy68]

Maybe i'm confused but I think you are misunderstanding the use of master pages/embedded pages. These only exist within WB when creating pages. They help you re-use the same info among several pages and make easier to change something by only having to change it in one place. When you publish/preview, your page and master page/embedded pages are merged into 1 page. The CSS and JS that are loaded for each page is unique to each page created. There is a global stylesheet also generated for the project which contains some basic styles for all pages.

When someone loads a page, many things are cached so that the page can reload quickly in the future. So for example, if an image is loaded on your home (index) page and the same image is present on your Services page it will load the image from the cache versus pulling from the server.

As for the 2 suggestions:
Eliminate render-blocking resources - typically this means that CSS and JS files should be loaded later rather than upfront. You have this done by moving CSS and JS files to the end of the page. This is available in the Tools --> options --> HTML section. (if memory serves me). Keep in mind, some things may not work when this is done as sometimes (not often) a js file may need to be loaded early.

Avoid chaining critical request - this basically means that critical resources needed to load the web page are overly large in size. There could be many reasons for this. One of the main causes of the “avoid chaining critical requests” warning is render-blocking resources. These render-blocking resources may include images, text-based resources, CSS files, or JavaScript files, causing the first rendering of content on your web page to slow down. So tackling the 1st one will help with this warning. Another thing that may help is to make sure you are minimizing your CSS and JS files. This can also be set in the options.

[benkn]

I would have thought that browser side caching will take care of any potential reloads. I don't use 'embedded' myself, but if you want to look at one of my sites (e.g. penninescouts.org.uk), the header, menu and logo are all in my master page. See how it 'feels' for speed when you move pages.

It may be that you have a solution looking for a problem.

Alan

Thanks Alan. site looks great and very fast. Im kinda nit-picking milliseconds.

curious why I cant right click on your site? I am trying to right click some images on your home page, to see the file sizes and compare. when I tried scrolling images it wasnt as smoth.

Thanks!

[benkn]

Maybe i'm confused but I think you are misunderstanding the use of master pages/embedded pages

No you were correct. I had little clue. I understand it better now, thank you so much!

I will experiment with loading css and js files after (yes tools/options/html). For, I am going to recheck image sizes and plow forward.

Thanks again!

[alan_sh]

I would have thought that browser side caching will take care of any potential reloads. I don't use 'embedded' myself, but if you want to look at one of my sites (e.g. penninescouts.org.uk), the header, menu and logo are all in my master page. See how it 'feels' for speed when you move pages.

It may be that you have a solution looking for a problem.

Alan

Thanks Alan. site looks great and very fast. Im kinda nit-picking milliseconds.

curious why I cant right click on your site? I am trying to right click some images on your home page, to see the file sizes and compare. when I tried scrolling images it wasnt as smoth.

Thanks!

I've disabled right clicking - it's one of the ready made scripts - so that people can't easily download pictures. I've also optimised the file sizes so that they are quick to load.

Alan