Performance benefits for "SVG Tiny 1.2" in today’s mobile & desktop browsers?

Question

I am trying to find the best way to export a complex vector graphic (i.e., an architectural plan, weighing in at several megabytes uncompressed) for optimal display on the web – and I wonder, if the generally recommended SVG 1.1 option in Illustrator is the best choice.

From what I've learned so far, Scalable Vector Graphics Tiny 1.2 specification...

• used to have limited viewer support, but not anymore.
• has no effect on file size; best way to reduce it is by shaving off unnecessary decimals with SVGO. — I suppose, other than the initial "baseprofile" parameter, an SVG Tiny 1.2 file will not structurally differ that much from an identical vector graphic saved as SVG 1.1.
• has some additional features that aren't available in other SVG flavours.
• offers a simplified DOM and discards some processor-intensive computations like clipping, masks, symbols, or SVG filter effects.

So, regarding the last point, I wonder: Are today's browsers – especially on smartphones – able to paint an SVG Tiny 1.2 file more efficiently and therefore faster, knowing that they may allocate fewer processing resources or can omit certain rendering steps?

Answer 1

Browsers have mostly skipped SVG 1.2 features and completely ignore baseProfile and version attributes.

The features from SVG 1.2 that have been cherry picked are:

• vector-effect non-scaling-stroke
• viewBox="none"

Firefox supports both of the above though I'm not sure any other UA supports viewBox="none"