Typek – Performance WordPress speed enhancing plugin

Our plugin is a comprehensive solution, which efficiently substitutes most of known premium plugins on the market. Only cache that is acceptable is server cache(litespeed cache etc.), or services such as cloudlflare etc.  

Most of the currently available tools on the market are based on http1 recommendations, meaning they merge .js files in big packages, which require more time to by analysed by the browser. The same goes for .css files.

Possible situation with standard plugin:
Your browser may need from 500ms to 1s to download one big (1mb) .css file.
The browser may need from 700ms to 1.5s to render such a big .css file.  
This means that during the first visit just the download and render of the .css file may take over 2.5 seconds. With each following visit the browser will not need to download the file, because it will be stored in cache, but rendering such a large file will still take up a long time – from 700ms to over 1.5s.

Typek Performance plugin generates smaller files for each website.

Downloading a file from 100kb to 200kb in size will take your browser about 100ms to 300ms.
Analysing a small file will take about 50ms to 200ms.    
During first visit and rendering it will take at maximum 500-700ms, meaning you can save up to 1.5 second. With repeated visit the saved time will be about 100ms to even few seconds depending on the size of the .css file.

To construct the render tree, a browser must PARSE HTML to DOM and CSS to CSSOM and then analyze the entire DOM tree and check which CSS rules apply to each node. The more unused CSS there is the more time the browser might potentially need to calculate styles for each node. Our plugin analyzes page structure and removes unnecessary code from css then it creates generates unique files containing only the required code for each page plugin.

It’s simple, the plugin supports the optimization for .js files – Plugin manager, load on scroll, http2 push

It’s simple, the website can load even up to 3 seconds, but the time before the user can use it may be 300ms – in other words, the user may use the site after 300ms and the rest of the less important content is loaded after. 
A good examples are: button for adding items into cart in online stores, analysis or facebook pixel.
Do you know anyone who clicks “Add to Cart” immediately after entering a site? – Me neither, that is why this script and others like it can be loaded later or when they are needed.  The same goes for analytics, Facebook pixel and other scripts Why load them first, if the user does not need them, you can wait 300-400ms and load them in the end. That is why your website can be fully loaded in 1.5s and be available after that time. And your competition’s website can load in full after 3 seconds, but be accessible and visible after only 300ms. Which means that the user can use the site freely, see all the content after 300ms, and the remaining elements such as tracking codes, pixels and other functions will be loaded during the visit.

Unfortunately, no. This may sound strange, but it is not a miracle tool, or panacea to all website-related ills. The biggest problem is us – website and plugin users. We install thousands of solutions on ready websites – this popup looks great, that plugin will show a cool button, here I need a giant slider, here we need a map and a script for chat. Every one of these features can be used on your website, but you should know how these plugins operate and how to avoid overloading DOM – e.g. Many sliders have bigger size and an entire theme. Yes, just one slider can generate a heavier load and your entire website. That one small pop-up can generate a heavier load and your entire website. Few dozen of such elements and DOM is too big for anyone to handle.

We will not pull wool over your eyes and promise you the impossible, there are no tools which can repair a website code – our plugin works great, but you need to remember that it’s intended to optimize the code, not fix it.  Typek Performance plugin does not repair third-party code, it only optimizes it. Remember that it works best if you use a balanced number of plugins, because it supports your work environment. Use fewer plugins. More plugins = more problems.

All of them are great, really – More pagebuilders has more than 750 functions and you probably only use 20 of them, and other users are use a 20 different functions from yours. Page builder developers are doing all they can so their tools work faster. In most cases it’s up to you how fast your website will be – we can handle most .css files with a correctly written theme, but big .js files might be a problem. If the publisher of your theme generates few mb of just .js files clustered into one… you’re gonna have a bad day.😊 

We use Shoptimizer and Gutenberg, which are great tools and is really well optimized.

There are so many variables and reasons why the plugin might not work in your instalations. That is why, we ask you to contact us.