wp_enqueue_global_styles()

Compatibility

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Performance profile

How much work a call to wp_enqueue_global_styles() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class

Moderate

Reads stored settings via get_transient(), cached per request but not free on a cold cache.

Scaling

Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions

13–73

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 92.

Plugin surface

None

Nothing here hands control to plugin code.

Called by

0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

• hookthird-party callbacksapply_filters()one call below wp_enqueue_global_styles()
• cacheobject cachewp_cache_get()one call below wp_enqueue_global_styles()
• transienttransientget_transient()one call below wp_enqueue_global_styles()

Further down the call graph this can also reach option, query and serialize. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 15 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_enqueue_global_styles() can have, taken from its control-flow graph on PHP 8.5.

Uses · 13

• wp_should_load_block_assets_on_demand()Checks whether block styles should be loaded only on-render.
• wp_is_block_theme()Returns whether the active theme is a block-based theme or not.
• doing_action()Returns whether or not an action hook is currently being processed.
• has_action()Checks if any action has been registered for a hook.
• wp_register_style()Registers a CSS stylesheet.
• wp_add_inline_style()Adds extra CSS styles to a registered stylesheet.
• wp_enqueue_style()Enqueues a CSS stylesheet.
• add_filter()Adds a callback function to a filter hook.
• wp_get_global_stylesheet()Returns the stylesheet resulting of merging core, theme, and user data.
• remove_action()Removes a callback function from an action hook.
• wp_get_custom_css()Fetches the saved Custom CSS content for rendering.
• is_customize_preview()Whether the site is being previewed in the Customizer.

Source code

View on Trac ↗View on GitHub ↗

2548function wp_enqueue_global_styles() {2549	$assets_on_demand = wp_should_load_block_assets_on_demand();2550	$is_block_theme   = wp_is_block_theme();2551	$is_classic_theme = ! $is_block_theme;2552 2553	/**2554	 * Global styles should be printed in the HEAD for block themes, or for classic themes when loading assets on2555	 * demand is disabled (which is no longer the default since WordPress 6.9).2556	 *2557	 * @link https://core.trac.wordpress.org/ticket/534942558	 * @link https://core.trac.wordpress.org/ticket/619652559	 */2560	if (2561		doing_action( 'wp_footer' ) &&2562		(2563			$is_block_theme ||2564			( $is_classic_theme && ! $assets_on_demand )2565		)2566	) {2567		return;2568	}2569 2570	/**2571	 * The footer should only be used for classic themes when loading assets on demand is enabled. In WP 6.9 this is the2572	 * default with the introduction of hoisting late-printed styles (via {@see wp_load_classic_theme_block_styles_on_demand()}).2573	 * So even though the main global styles are not printed here in the HEAD for classic themes with on-demand asset2574	 * loading, a placeholder for the global styles is still enqueued. Then when {@see wp_hoist_late_printed_styles()}2575	 * processes the output buffer, it can locate the placeholder and inject the global styles from the footer into the2576	 * HEAD, replacing the placeholder.2577	 *2578	 * @link https://core.trac.wordpress.org/ticket/640992579	 */2580	if ( $is_classic_theme && doing_action( 'wp_enqueue_scripts' ) && $assets_on_demand ) {2581		if ( has_action( 'wp_template_enhancement_output_buffer_started', 'wp_hoist_late_printed_styles' ) ) {2582			wp_register_style( 'wp-global-styles-placeholder', false );2583			wp_add_inline_style( 'wp-global-styles-placeholder', ':root { --wp-internal-comment: "Placeholder for wp_hoist_late_printed_styles() to replace with the global-styles printed at wp_footer." }' );2584			wp_enqueue_style( 'wp-global-styles-placeholder' );2585		}2586		return;2587	}2588 2589	/*2590	 * If loading the CSS for each block separately, then load the theme.json CSS conditionally.2591	 * This removes the CSS from the global-styles stylesheet and adds it to the inline CSS for each block.2592	 * This filter must be registered before calling wp_get_global_stylesheet();2593	 */2594	add_filter( 'wp_theme_json_get_style_nodes', 'wp_filter_out_block_nodes' );2595 2596	$stylesheet = wp_get_global_stylesheet();2597 2598	/*2599	 * For block themes, merge Customizer's custom CSS into the global styles stylesheet2600	 * before the global styles custom CSS, ensuring proper cascade order.2601	 * For classic themes, let the Customizer CSS print separately via wp_custom_css_cb()2602	 * at priority 101 in wp_head, preserving its position at the end of the <head>.2603	 */2604	if ( $is_block_theme ) {2605		/*2606		 * Dequeue the Customizer's custom CSS2607		 * and add it before the global styles custom CSS.2608		 */2609		remove_action( 'wp_head', 'wp_custom_css_cb', 101 );2610 2611		/*2612		 * Get the custom CSS from the Customizer and add it to the global stylesheet.2613		 * Always do this in Customizer preview for the sake of live preview since it be empty.2614		 */2615		$custom_css = trim( wp_get_custom_css() );2616		if ( $custom_css || is_customize_preview() ) {2617			if ( is_customize_preview() ) {2618				/*2619				 * When in the Customizer preview, wrap the Custom CSS in milestone comments to allow customize-preview.js2620				 * to locate the CSS to replace for live previewing. Make sure that the milestone comments are omitted from2621				 * the stored Custom CSS if by chance someone tried to add them, which would be highly unlikely, but it2622				 * would break live previewing.2623				 */2624				$before_milestone = '/*BEGIN_CUSTOMIZER_CUSTOM_CSS*/';2625				$after_milestone  = '/*END_CUSTOMIZER_CUSTOM_CSS*/';2626				$custom_css       = str_replace( array( $before_milestone, $after_milestone ), '', $custom_css );2627				$custom_css       = $before_milestone . "\n" . $custom_css . "\n" . $after_milestone;

Changelog

Introduced in 5.8.0. Unchanged from 6.7.7 through 7.1.0.

1. 6.7.7
2. 6.8.8
3. 6.9.7
4. 7.0.4
5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data

Generated from the wordpress-develop 7.0.4 tag, from src/wp-includes/script-loader.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.

Corrections

Something wrong on this page? Report it and it gets fixed in the next regeneration.