@adrianakstein Analyse and prioritise by:
1) The biggest bottlenecks
2) Earliest in the chain
3) That impacts the most pages
4) Of pages that are important to the business
5) And strongest with traffic/SEO
Or ...
Just work from improving TTFB through to serving images based on display.
:D
1) The biggest bottlenecks
2) Earliest in the chain
3) That impacts the most pages
4) Of pages that are important to the business
5) And strongest with traffic/SEO
Or ...
Just work from improving TTFB through to serving images based on display.
:D
@adrianakstein Actual "optimisations"?
Depends on what the issues are, and what's already done ... but ...
CDNs will sort most issues.
Alternatively:
* PreConnect
* PreLoad
* Load priorities
* Compression
* Minification
* Reduce resource requests (images, CSS, JS)
>>>
Depends on what the issues are, and what's already done ... but ...
CDNs will sort most issues.
Alternatively:
* PreConnect
* PreLoad
* Load priorities
* Compression
* Minification
* Reduce resource requests (images, CSS, JS)
>>>
@adrianakstein >>>
* Embed vital/critical resources (dataURI, CSS in <style> in <head>, JS in <script> bottom of <head> or bottom of <body>)
* Prioritise resource load order (CSS before JS, JS after "content" when possible" etc.)
* Serve images with dimensions to suit Res.
>>>
* Embed vital/critical resources (dataURI, CSS in <style> in <head>, JS in <script> bottom of <head> or bottom of <body>)
* Prioritise resource load order (CSS before JS, JS after "content" when possible" etc.)
* Serve images with dimensions to suit Res.
>>>
@adrianakstein >>>
* Consider ditching "libraries" and using "vanilla" JS if applicable
* Utilise server caching mechanisms (OpCode, Memchached, manual stores etc.)
* Utilise platform caching mechanisms (save "pages" to avoid regeneration, and the processing/queries etc.)
>>>
* Consider ditching "libraries" and using "vanilla" JS if applicable
* Utilise server caching mechanisms (OpCode, Memchached, manual stores etc.)
* Utilise platform caching mechanisms (save "pages" to avoid regeneration, and the processing/queries etc.)
>>>
@adrianakstein >>>
* Tweak server config (allocated RAM etc.)
* Consider improving platform code base (reduce number of queries, larger query and sort/filter etc.)
* Utilise user-info headers (data-save, viewport dimensions etc.) and server appropriately for images/CSS
>>>
* Tweak server config (allocated RAM etc.)
* Consider improving platform code base (reduce number of queries, larger query and sort/filter etc.)
* Utilise user-info headers (data-save, viewport dimensions etc.) and server appropriately for images/CSS
>>>
@adrianakstein * deploy CSS's content-visibility and contain-intrinsic-size
* simplify the DOM structure (reduce number of elements and levels of nesting)
* simplify the CSS layout
* use Lazy loading (now supported in most browsers as an image attribute)
>>>
* simplify the DOM structure (reduce number of elements and levels of nesting)
* simplify the CSS layout
* use Lazy loading (now supported in most browsers as an image attribute)
>>>
@adrianakstein >>>
There's no shortage of things you can do to speed things up ...
... but a CDN will handle most (esp. reducing RTT/Latency, and TTFB).
And remember - it's a case of diminishing returns,
each additional improvement will typically yield less improvement, down to mere ms.
There's no shortage of things you can do to speed things up ...
... but a CDN will handle most (esp. reducing RTT/Latency, and TTFB).
And remember - it's a case of diminishing returns,
each additional improvement will typically yield less improvement, down to mere ms.
Loading suggestions...