[{"data":1,"prerenderedAt":90},["ShallowReactive",2],{"\u002Fglossary\u002Fbaseline":3,"\u002Fglossary\u002Fbaseline:related":73},{"id":4,"title":5,"author":6,"authorImage":7,"body":8,"category":58,"date":59,"description":60,"draft":61,"extension":62,"letter":63,"meta":64,"navigation":65,"path":66,"readTime":67,"related":68,"seo":69,"stem":71,"term":5,"__hash__":72},"glossary\u002Fglossary\u002Fbaseline.md","Baseline","Fabian Krumbholz","\u002Fimages\u002Fauthors\u002Ffabian-krumbholz.webp",{"type":9,"value":10,"toc":54},"minimark",[11,18],[12,13,14,17],"p",{},[15,16,5],"strong",{}," is a standard that indicates when a web platform feature is broadly supported and safe to use across all major browsers. While Baseline itself has two official statuses, a feature's complete journey to widespread adoption can be seen in three main stages:",[19,20,21,32,45],"ul",{},[22,23,24,27,28,31],"li",{},[15,25,26],{},"Experimental",": The stage ",[15,29,30],{},"before"," a feature enters Baseline. It is typically supported by only one or two browser engines, is not yet interoperable, and is not recommended for production use.",[22,33,34,37,38,41,42],{},[15,35,36],{},"Newly available",": The ",[15,39,40],{},"first official Baseline status",". A feature achieves this status once it is supported by all major browser engines (Chrome\u002FEdge, Firefox, and Safari). It is now safe to start using in production.",[15,43,44],{},"‍",[22,46,47,37,50,53],{},[15,48,49],{},"Widely available",[15,51,52],{},"mature Baseline status",". A feature achieves this after it has been \"Newly available\" for 30 months, ensuring it has had ample time to roll out to the vast majority of users worldwide, making it extremely safe to use.",{"title":55,"searchDepth":56,"depth":56,"links":57},"",2,[],null,"October 9, 2025","Baseline is a standard that indicates when a web platform feature is broadly supported and safe to use across all major browsers.",false,"md","B",{},true,"\u002Fglossary\u002Fbaseline","1 min read",[],{"title":70,"description":60},"Baseline: Definition | Web Performance Glossary","glossary\u002Fbaseline","sZ0uY8MV2RI0c7YBb9ARzzFCwJ668HG473Bt8iyfNgk",[74,78,82,86],{"path":75,"title":76,"description":77,"letter":63},"\u002Fglossary\u002Fback-forward-cache-bfcache","Back\u002FForward Cache (bfcache)","The back\u002Fforward cache (or bfcache) is a browser optimization that enables instant navigations when a user clicks the back or forward buttons.",{"path":79,"title":80,"description":81,"letter":63},"\u002Fglossary\u002Fbackend","Backend","The backend refers to the server-side components of a web application that are not visible to the end-user. This includes the web server, application logic, and databases.",{"path":83,"title":84,"description":85,"letter":63},"\u002Fglossary\u002Fbackend-cache-aws","Backend Cache (AWS)","This is Speed Kit's central, primary cache where Anonymous HTML and other website assets are stored. It is hosted on Amazon Web Services (AWS), a secure and highly reliable cloud computing platform.",{"path":87,"title":88,"description":89,"letter":63},"\u002Fglossary\u002Fbackend-time","Backend Time","Backend Time is the duration it takes for a website's Origin Server to process a request and generate the HTML for a page.",1787756711609]