FAQ

A list of answers to common questions.

How does Edgemesh compare to X?

First thing you want to ask yourself is "Do they even compare"? Most of the time when we get this question, people are asking about an acceleration platform that is deployed server side. Edgemesh requires no server side deployments. Is one better than the other? No. In fact, having a well configured server allows Edgemesh to run at its maximum capacity. If any misconfigurations are discovered, Edgemesh will do its best to deterministically correct them. If it is unable to, you will be alerted. While server side acceleration platforms generally do what they advertise, if the choice came down to either or, choose Edgemesh. The server can be optimized by hand one time and then you are done forever. We offer professional services to optimize server side configurations and a free audit is included with every Enterprise plan.

Is Edgemesh compatible with X?

In most cases the answer is yes. The only time you will run into issues is if you are using another service with a Service Worker implementation that overrides the onFetch event.

What content can Edgemesh Accelerate?

What a handsome looking question! Edgemesh is capable of caching the following assets types:

Images

bmp, bpg, eps, gif, ico, jpeg, jpg, pict, png, svg, svgz, tif, tiff, webp

Video

amv, avi, drc, f4bogv, f4p, f4v, flv, gifv, m2v, m4v, mkv, mov, mp2, mp4, mpe, mpeg, mpg, mpv, qt, webm, wmv, 3g2, 3gp

Fonts

otf, ttf, woff, eot

Audio

aac, aiff, f4a, flac, m4a, m4p, mid, midi, mogg, mp3, ogg, oga, opus, ra, rm, wav, webm

Stylesheets

css

Application

js, swf, wasm, wat

Archives

apk, bz2, dmg, gz, iso, jar, lz, lzma, rar, tar, tbz2, tgz, tlz, txz, xz, z, zip, zipx, 7z

Documents

doc, docx, otf, pdf, ppt, pptx, ps, xls, xlsx

Does Edgemesh accelerate the first load?

The very first time a user visits your site after installation, Edgemesh initializes itself on the user's browser. On most sites this takes around 200ms. Once Edgemesh is initialized, your site is accelerated from that point on. When a visitor returns to your site, they are fully accelerated for the entire session. Edgemesh can improve the first load because it is able to catch and cache the tail of the website. Often times Edgemesh will start up and will have had optimistically cached the rest of the content for the page before the browser has requested it.

Also, it's important to note that search engines like Google use all page loads to determine ranking, not just the first load. You can read more at docs.crux.run.

How does Edgemesh work on Shopify?

When you add the Edgemesh App to your Shopify store, the scripttag API will be utilized to add the two required Edgemesh scripts to the <head> tag of your site. There will be two files added: client.js, the Edgemesh client and shopify.js, the Edgemesh initialization for Shopify. If you decide you want to remove Edgemesh, simply delete the App from your store. Shopify will automatically remove the two script tags which in turn prompts Edgemesh to unmount all running service workers (client-side caches). The Edgemesh Shopify App does not use any other Shopify API's. We do not alter your theme, storefront or back end in any way.

What are these opaque asset warnings and errors I see in my console?

An opaque asset is an asset with CORS (cross origin resource sharing) disabled. As a safety precaution, Edgemesh does not attempt to cache any asset that it can not read the Cache-Control header on. Unfortunately this includes all opaque assets. There are a few valid reasons to set an asset as opaque, but in most cases we find that this is a misconfiguration. As Edgemesh discovers these opaque requests, our team reaches out to the vendor to determine if CORS is disabled intentionally. If so, we add the resource to our global blacklist. At that point you will no longer see the warning, but we are sadly unable to cache the resource.

A little more about the warnings and errors:

Edgemesh tries to fetch all assets with no-cors mode. If the initial request fails, Edgemesh allows the browser to perform the original request. The resource is then flagged for further investigation by the Edgemesh team and you are presented with an error (from the browser) and a warning (from Edgemesh) explaining the error. The warning is there to let you know everything is in fact ok, but it could be better. The impact of performing a second request for a few resources on a site is heavly out weighed by the performance you gain from the rest of the properly configured page. In the case of an error, all that was exchanged is header information. It's generally very quick to verify if an asset can be cached.

Depending on your platform and architecture these "errors" could be something you can fix, but more often than not it's on a third party vendor. Edgemesh will handle these vendor resources on a case by case basis and nothing will be required from an Edgemesh customer to reap the ongoing benefits of our internet network research.

How does Edgemesh deal with cache invalidation?

See Cache Invalidation.

‚Äč