Our servers automatically detect which device is making a request and serves an appropriate image. There is no reason why you should be serving the same image to both a low-powered mobile device and a high-end desktop.
Your images are automatically converted to a wide range of formats including Webp (for Chrome, Opera), progressive images (for lower bandwidth conditions) and served accordingly.
All the optimized assets are served via AWS Cloudfront's globally distributed CDN. Images are served with lowest possible latency for your users all around the world.
Service workers are like proxies that run in your browser which can be controlled via JS. Using this, we route all image requests through our optimising servers at runtime.
Browsers expose the Service Worker API only on secure origins. If your site is not yet on HTTPS, we recommend you check out Let's Encrypt - its simple, and free.
Host the script emailed to you on your server root. The script must be accessible at http://yourwebsite.com/script.js. If you are unable to host the script on the server root, check out Service-Worker-Allowed header for alternative options.
We will look into why this website did not work.
We have sent you an email with the steps for optimising your site.
Follow the steps in the email, just hit reply with any queries.
Reach out to us in case of any problem.
Dexecure has helped us greatly improve the performance of our website. The solution fits nicely into our architecture and optimising new web pages is very easy and seamless. Not just the solution is great, but also the support from its team is fantastic.
Dexecure worked like magic for us - we ended up with a 2.5x improvement in load time just from better image compression. Unless you want to optimize your images yourself for all browsers and on all platforms this is the way to go.
Dexecure has made optimising our image heavy website effortless and blazingly fast which is vital to our business.
In the unlikely event our server goes down, the script still makes a request back to your original server to retrieve the unoptimized images (bypassing our server entirely). Your users will not notice any visual difference to the page.
We rely on the Service Worker API which the browsers have exposed only on HTTPS origins for security reasons.
You are? High five! Since only one service worker can operate in a given page at a time, you will have to merge our service worker logic into your own. Our service worker logic is extremely light-weight and can be found in our open source repository here
Yes. Though the test in this page cannot scan behind a login, our script can work well with dynamic pages (or SPA) behind a login too! Go ahead and try it out.
We create a new AWS Cloudfront distribution just for you! It will host all your optimized images and this takes around 15 minutes to set up completely.
We optimize a image for a particular configuration only once. After it has been optimized, they are directly served via Amazon Cloudfront CDN without hitting our servers.
We try to replicate your existing cache headers when serving optimized images. We enforce a minimum cache time of 4 hours.
Our optimisations kick in only when a outbound network request takes place. If images are hosted on your own local host, our servers are unable to access them. We recommend trying it out on websites which are hosted online.
You should see the average page size and the load times reduce in the developer tools of your favourite browser or in monitoring tools that you may have set up such as New Relic, etc.
Sure, just make sure that the script installation call from the HTML file points to the right location. Also since the script is a Service-Worker, a script installed in a sub-directory can only control pages within that sub-directory. To get around this limitation, you should set a particular response header for the Service-Worker. Read more about the Service-Worker-Allowed header here.
Is the error occuring on a URL that is of the format *.cloudfront.net? If so, it means that AWS is creating a distribution for you - this process usually takes upto 15 minutes. There should be no visual difference to your website at this time. Once it is ready, the error will be resolved automatically. In case the error persists, contact us.
Unclean code drives him nuts. Tech nerd, coder by day and gamer by night.
Web security shifu. Specializes in building secure systems interfacing with the cloud, web and personal devices.
Veteran business strategist and venture builder. He can recite the specs of any race car even in the middle of his sleep.
Venture capitalist, and CEO of research lab. Enjoys the thrills and spills of breakthrough ideas, as he does Alpine skiing.