Decreased mobile load time by 15+seconds with preload key request but still have small error

TLDR - Is there ANY other way to do a preload key request with wix. PLEASE! It shaves off so much time it’s insane.

So running the google pagespeed test, it tells me to use preload key requests to speed up the website. " Preload key requests 14.04 s Consider using to prioritize fetching resources that are currently requested later in page load."

It literally would increase page load time by 14 seconds, which is ridiculous.

I was able to pop this code line into the ‘tracking and analytics’ because that’s the easiest way to get an html code on all pages. <link rel=‘preload’ href="https://www.hydrochemsystems.com/_partials/wix-bolt/1.2670.0/node_modules/santa-wix-code/dist/bolt-worker.js>

It works on every page except the home page. The number within the code “1.2670.0” does seem to change, and I wonder if there’s a preload request that’s more basic that wouldn’t change. It also shows code at the top of the pages when switch between them or on a refresh, causing the menu bar to disappear.

I’ve tried “” but google says

Warnings: A preload was found for “https://www.hydrochemsystems.com/_partials/wix-bolt/1.2687.0/node_modules/santa-wix-code/dist/bolt-worker.js” but was not used by the browser. Check that you are using the crossorigin attribute properly.

I’ve tried the crossorigin as crossorigin, crossorigin=“anonymous” crossorigin=“” and crossorigin=“use-credentials”.

I don’t know what else to do but this is a massive game changer if I can just get it to work and not mess up the refresh.

3 Likes

Okay, I was able to break it down even further to <link rel=‘preload’ href="https://static.parastorage.com/> in the header, using a specific page to test.

It’s fantastic BUT it still does weird thing upon refresh and everything on my menu bar disappears. I think I’m missing the follow up within this code or the first. Both work, but both have minor errors.

I will leave it active on this specific page as an example if anyone is willing to help. It’s probably our lowest traffic page. https://www.hydrochemsystems.com/parts-washers

The image is an example of what happens right before the page loads.

I use <link rel=“dns-prefetch” etc on my website already.

However, to use it you will need to put it in the SEO tab that you can reach through your Wix Editor and going to Settings in the top menu.

You can use one of the five options here.

<link rel="prefetch" href="/style.css" as="style" />
<link rel="preload" href="/style.css" as="style" />
<link rel="preconnect" href="https://example.com" />
<link rel="dns-prefetch" href="https://example.com" />
<link rel="prerender" href="https://example.com/about.html" />

Don’t overuse it. Preloading everything won’t magically speed up the site – instead, it will likely prevent the browser from scheduling everything smartly.

The prefetch and preconnect don’t really help with my site specifically. I’m not particularly concerned with page to page speed, but initial load time.

The preload code works, but I can’t figure out how to make it not error out - Can you preload…a CDN? The parastorage.com is what speeds it up drastically.

The preload link can be specified by the developer, or be automatically generated by the application server or an optimization proxy (e.g. a CDN).
https://www.w3.org/TR/preload/

DNS prefetching can be added to a specific URL by adding the rel=”dns-prefetch” tag to the link attribute.
I suggest using this for things such as Google fonts, Google Analytics and your CDN.

At any time you load a resource that the very first thing occurs is DNS lookup. If the resource is local to your domain, then the dns lookup has already happened so there’s not much help there. But if you use a CDN, or are loading scripts from another domain, it will help to have the DNS already looked up.

These are the ones that I have used for my site.

href="//fonts.googleapis.com"
href="//static.wixstatic.com"
href="//static.parastorage.com"
href="//site-pages.wix.com"
href="//wix-code.com"
href="//maps.googleapis.com"
href="//frog.wix.com"
href="//gstatic.com"

When you say you’ve used them, do you pick a few, just one, or use them all?

I can’t get the dns prefetch to do anything faster

so far the ONLY thing that changes it is whether or not I close the link with a "

example that works

I use all of them as this.

<link rel="dns-prefetch" href="//fonts.googleapis.com">
<link rel="dns-prefetch" href="//static.wixstatic.com">
<link rel="dns-prefetch" href="//static.parastorage.com">
<link rel="dns-prefetch" href="//site-pages.wix.com">
<link rel="dns-prefetch" href="//wix-code.com">
<link rel="dns-prefetch" href="//maps.googleapis.com">
<link rel="dns-prefetch" href="//frog.wix.com">
<link rel="dns-prefetch" href="//gstatic.com">

Also, you might want to look at cache control
Cache-Control - HTTP | MDN

Along with DNS Prefetch Control if you are looking at using it.
X-DNS-Prefetch-Control - HTTP | MDN

For more about preload see here.
rel=preload - HTML: HyperText Markup Language | MDN
Redirecting to the HTML spec

Any updates on this? bolt-worker.js is killing my load times, as well.

No, unfortunately I think we’ll end up at wordpress within a year. I’ve done everything physically possible to speed up my site and…it’s not enough.

@amandaheyn This is my first time on the board - are there any Wix people here who can weigh in?

@admin8521 Occasionally they will. I posted this all over everywhere - other forums, reddit, etc. It’s a wix thing and it’s not possible to preload them for whatever reason. I’ll see if I can find the response from the wix people telling me this.

@admin8521 https://www.wix.com/corvid/forum/community-discussion/preload-key-requests

Hi all
I’m no expert but I will try to explain.
It’s GLOBALLY applied script


You can’t prelaod that because it is set to prefetch .

Because this script is applied your header look like this, and have low score. I have same problem too.

If you look closely it look like this:

https://static.parastorage.com/; rel=preconnect; crossorigin,
https://fonts.gstatic.com; rel=preconnect; crossorigin,
https://static.parastorage.com/unpkg/requirejs-bolt@2.3.6/requirejs.min.js; rel=preload; as=script;,
https://static.parastorage.com/unpkg/lodash@4.17.15/lodash.min.js; rel=preload; as=script ; crossorigin=anonymous;,
https://static.parastorage.com/unpkg/zepto@1.2.0/dist/zepto.min.js; rel=preload; as=script ; crossorigin=anonymous;,
https://static.parastorage.com/services/wix-bolt/1.3867.0/bolt-main/app/main-r.min.js; rel=preload; as=script ; crossorigin=anonymous;

It also add one duplicate (in my opinion):

https://static.wixstatic.com/; rel=preconnect;,
https://static.wixstatic.com/; rel=preconnect; crossorigin;,

If you want to speed up your site, try dns-prefetch. I had luck with this

<link rel="dns-prefetch" href="//static.parastorage.com">
<link rel="dns-prefetch" href="//frog.wix.com">
<link rel="dns-prefetch" href="//static.wixstatic.com">
<link rel="dns-prefetch" href="//siteassets.parastorage.com">

Thanks, however that was already mentioned on 8th June. :wink:

All been working fine and fast since I implemented mine too.

I have better result without

<link rel="dns-prefetch" href="//wix-code.com">

It should look something like this if you want to be resolved

<link rel="dns-prefetch" href="//77df02c4-af50-4fa0-aaaa-4a75e65169f6.static.pub.wix-code.com">

But we still have problem with preloading of partial bolt-worker.js

Do you feel any real improvement by using it? Does it load faster?

@jonatandor35 I tried that way. it is even slower. And if it’s faster, I’d have to check and change the generic number in front of
wix-code.com from time to time. I would waste a lot of time on that

@zokierc I’m not asking about the wix-code.com specifically. I’m wondering if any of the dns-prefetch had any significant effect.
Do you feel it speeds up anything?

@jonatandor35 Yes. I had 9 for mobile at PageSpeed Insights. Now have 39 :slight_smile:
Go to webpagetest.org and test your site. Look at domains tab and add 3 to 4 domains with most connections. Don’t put to many because you will lose performance. Look at waterfall and put in that order dns-prefetch too.
DDD