- From: Hans Polak <info@polak.es>
- Date: Mon, 29 Aug 2022 17:29:22 +0200
- To: public-schemaorg@w3.org
- Message-ID: <d5e4c74d-381a-f102-7f1f-160837d5e412@polak.es>
Good afternoon, This is from StackOverflow. https://stackoverflow.com/questions/30864619/does-json-ld-have-to-be-embedded <link href="/myid123/jsonld.js" rel="alternate" type="application/ld+json" /> Yours sincerely, Hans Polak On 27/8/22 19:17, Roger Rogerson wrote: > I appreciate that things like MicroData are inlined, > and utilise the HTML Markup to associate data with content. > > But JSON-LD Schema is embedded. > In many cases, this additional code serves no "human" purpose, > and is provided for "machines" (typically Google). > > A shining example is the following web page (remove spaces after periods): > https://www. delish. com/cooking/g1956/best-cookies/ > > That page has approximately 35Kb of Schema. > That is loaded for every single human visitor. > > In the case of popular pages - this means a large amount of unnecessary > code is transferred (Gigabytes or higher per year). > > If the JSON-LD could be externalised into a referred to file, > then this could reduce bandwidth consumption for users, > help speed up some page load times/improve performance > and help towards "going green". > > > I appreciate that technically, > this isn't about "Schema" directly, > but about how Browsers and Parsers can recognise and handle > and externalised version - but I'm hoping this is the right place > to get it considered and the right people to see it/push it to browser > vendors. > > > Thank you. > Autocrat.
Received on Monday, 29 August 2022 15:29:39 UTC