bibliography, etc.), diagrams and images, tables and lists, Wikilinks and external URLs, and formatting and mark-up. The following script is helpful for estimating readable prose size: Lists, tables, and other material that is already in summary form may not be appropriate for reducing or summarizing further by the summary style method. If there is no "natural" way to split or reduce a long list or table, it may be best to leave it intact, and a decision made to either keep it embedded in the main article or split it off into a stand-alone page. Regardless, a list or table should be kept as short as is feasible for its purpose and scope. Too much statistical data is against policy Lists, tables, and other material that is already in summary form may not be appropriate for reducing or summarizing further by the summary style method. If there is no "natural" way to split or reduce a long list or table, it may be best to leave it intact, and a decision made to either keep it embedded in the main article split into a stand alone page Regardless, a list or table should be kept as short as is feasible for its purpose and scope. Too much statistical data is against policy. Total article size should be kept reasonably low, because many users edit from low-speed connections including dial-up connections, smart phones and low-end broadband connections. The text on a 32kB page takes about five seconds to load for editing on a dial-up connection, with accompanying images taking additional time, so pages significantly larger than this are difficult for older browsers to display. Articles of about 200kB (~30 pages) are not uncommon for topics that require depth and detail, but it's typical that articles of such size gets split up into two or more sub-articles.
bibliography, etc.), diagrams and images, tables and lists, Wikilinks and external URLs, and formatting and mark-up. The following script is helpful for estimating readable prose size: Lists, tables, and other material that is already in summary form may not be appropriate for reducing or summarizing further by the summary style method. If there is no "natural" way to split or reduce a long list or table, it may be best to leave it intact, and a decision made to either keep it embedded in the main article or split it off into a stand-alone page. Regardless, a list or table should be kept as short as is feasible for its purpose and scope. Too much statistical data is against policy Lists, tables, and other material that is already in summary form may not be appropriate for reducing or summarizing further by the summary style method. If there is no "natural" way to split or reduce a long list or table, it may be best to leave it intact, and a decision made to either keep it embedded in the main article split into a stand alone page Regardless, a list or table should be kept as short as is feasible for its purpose and scope. Too much statistical data is against policy. Total article size should be kept reasonably low, because many users edit from low-speed connections including dial-up connections, smart phones and low-end broadband connections. The text on a 32kB page takes about five seconds to load for editing on a dial-up connection, with accompanying images taking additional time, so pages significantly larger than this are difficult for older browsers to display. Articles of about 200kB (~30 pages) are not uncommon for topics that require depth and detail, but it's typical that articles of such size gets split up into two or more sub-articles.