H2S33: Speed optimizations for WordPress:

H3S1: Load texting as a proxy correlator to speed optimization:<Turing>

H3S2: HTML in the front, party in the back<Turing>:

<X.ref-Hubspot,a.r>: Hu: Whenever possible #, we should minimize on.request-assembly, and try to load as many pages, as we can, as static | HTML, with a combination of intelligent | design and precaching, and, potentially, lazy-loading dynamic | elements, while front-loading the HTML pages, first. This exposes a key philosophical | difference between my philosophy and that of WP, that any web-page, in fact, can be loaded as PHP.

H3S3: Load.time-factors:

H4S1: loading files, straight bandwidth, from db.

H4S2: MySQL query: what returns can be 50 bytes and cost 0 bandwidth, but you don’t start to get that data, until the query is done, and the query time depends on the number of rows searched.

H4S3: Conditional depth in script.

H4S4: Physical distance traveled by data.

H4S5: Loops, specified in PHP, but whose execution may trigger, chained, other actions that also affect page speed, by having their own loading component, multiplied.[E: Multiplicative]




Leave a Reply

Your email address will not be published. Required fields are marked *