How a page’s text brings code along
A browser does not receive a webpage as one finished sheet. It reads instructions in the page’s HTML—the underlying document—and follows references to other files. A reference to a JavaScript file can prompt another download, much as a recipe can call for ingredients stored elsewhere.
JavaScript is code that lets a page respond to clicks, update content, or run other functions. A site may also include code for measuring visits, serving ads, or connecting to outside services. These scripts are not visible as paragraphs, but the browser may still need to fetch and process them before the page is fully ready.
One script can lead to more work
A script can ask the browser to retrieve additional code or send information to another server. That creates a chain of network requests beyond the original page. The browser also has to interpret and run the code, using processor time and memory; a slow connection can make each extra download more noticeable.
The amount varies widely. A mostly static page may need little beyond its text and images, while a page assembled from several services can load many separate files. Some scripts provide features visitors use; others support measurement or advertising. Their presence alone does not tell you what a script collects or whether it is necessary.
The practical consequence is that a page’s apparent simplicity can be misleading: a short article may arrive quickly, while the browser continues fetching and working through code that never appears on screen.
