Div nesting div speed will be equally slow

---restore content starts---

Div is nested in div speed will be equally slow

Recently, many bosses in our company to do business station will be asked to say: I want to div+css, do not form the kind of building, that is not conducive to optimization. But we found that even the websites they made in the form of Div+css did not see what optimizations they had done, and even the articles had not been updated. This is a digression, we have to talk about it is really used div+css made out of the website on the speed of open, the search engine is friendly? About the advantages of DIV+CSS is actually a lot, this layout method greatly reduced the page code, reduce the volume of the page, facilitate the reading of the page. The layout of table was originally used by a person responsible for the newspaper typesetting, his "invention" for the internet can be said to have played a significant role in promoting. Let the traditional Web page realize the colorful color and the layout structure. In the early days of Internet development, the use of more browsers is not IE, but the United States of several browser coexistence situation, and then Microsoft by the IE and Windows bundled to get rapid development. Until the end of the organization of the Code after the specification of the table has also been rapid development. Then with the development of the Internet, people's demand for speed is more and more high, and table because of its innate defects lead people to look for new ways to replace it, this appeared the DIV+CSS Web page production way. Say so much is to let everyone understand the history of these two typography, so can only say that Div+css is now more popular and more practical layout, and you can not say that table is not good, some of the functions of table is div+css currently can not be replaced. Again, what is called div+css abuse. We all know why we don't like to use table, because table typesetting is a lot of places where we need nested ways to implement the pages we need. And if the page has a lot of this kind of nesting then your page volume will be greatly increased, and the browser is read from the <table> to </table> in the order to read, it only when the entire table is finished reading the page can be rendered. If you nest too much, you can imagine how fast your page will be. The browser also follows this principle for page reads in the form of Div+css, which is also read from <div> to </div>. Then if your page div nested a lot of div speed will be also very slow, and nested too many div is very easy to appear browser incompatibility problems. So what's the difference between a page that you do and a table nesting? This is what we are going to say about the div abuse situation. A div can be completely implemented without having to define a style for the sake of convenience. So how do you avoid this happening? This requires a Web page to be refactored, for the concept of Web refactoring, you can go to Baidu search for a bit. This is a meticulous work, but also a very test of the ability of Web designers to live. If you know the CSS and a little bit of a div, your site is open-source CMS to do, then you can reconstruct the Web page. Modify the template, but you must be aware of the browser's compatibility during the process of modification. In fact, many of our websites and browsers are not compatible with the problem is mostly because of improper use of Div, or too much abuse caused. Table compatibility with the browser is much better, if an effect using a div will inevitably do a lot of nesting, or use table better. That is to use div+css and table to make the page, in order to achieve the maximum page code to streamline, without losing the effect. After reading these you should understand that is not div+css is certainly good, the same page effect some web designers with only a few div can be easily implemented, and some web designers have to use more than the former twice times or even several times of code.

---restore content ends---

Div is nested in div speed will be equally slow

Recently, many bosses in our company to do business station will be asked to say: I want to div+css, do not form the kind of building, that is not conducive to optimization. But we found that even the websites they made in the form of Div+css did not see what optimizations they had done, and even the articles had not been updated. This is a digression, we have to talk about it is really used div+css made out of the website on the speed of open, the search engine is friendly? About the advantages of DIV+CSS is actually a lot, this layout method greatly reduced the page code, reduce the volume of the page, facilitate the reading of the page. The layout of table was originally used by a person responsible for the newspaper typesetting, his "invention" for the internet can be said to have played a significant role in promoting. Let the traditional Web page realize the colorful color and the layout structure. In the early days of Internet development, the use of more browsers is not IE, but the United States of several browser coexistence situation, and then Microsoft by the IE and Windows bundled to get rapid development. Until the end of the organization of the Code after the specification of the table has also been rapid development. Then with the development of the Internet, people's demand for speed is more and more high, and table because of its innate defects lead people to look for new ways to replace it, this appeared the DIV+CSS Web page production way. Say so much is to let everyone understand the history of these two typography, so can only say that Div+css is now more popular and more practical layout, and you can not say that table is not good, some of the functions of table is div+css currently can not be replaced. Again, what is called div+css abuse. We all know why we don't like to use table, because table typesetting is a lot of places where we need nested ways to implement the pages we need. And if the page has a lot of this kind of nesting then your page volume will be greatly increased, and the browser is read from the <table> to </table> in the order to read, it only when the entire table is finished reading the page can be rendered. If you nest too much, you can imagine how fast your page will be. The browser also follows this principle for page reads in the form of Div+css, which is also read from <div> to </div>. Then if your page div nested a lot of div speed will be also very slow, and nested too many div is very easy to appear browser incompatibility problems. So what's the difference between a page that you do and a table nesting? This is what we are going to say about the div abuse situation. A div can be completely implemented without having to define a style for the sake of convenience. So how do you avoid this happening? This requires a Web page to be refactored, for the concept of Web refactoring, you can go to Baidu search for a bit. This is a meticulous work, but also a very test of the ability of Web designers to live. If you know the CSS and a little bit of a div, your site is open-source CMS to do, then you can reconstruct the Web page. Modify the template, but you must be aware of the browser's compatibility during the process of modification. In fact, many of our websites and browsers are not compatible with the problem is mostly because of improper use of Div, or too much abuse caused. Table compatibility with the browser is much better, if an effect using a div will inevitably do a lot of nesting, or use table better. That is to use div+css and table to make the page, in order to achieve the maximum page code to streamline, without losing the effect. After reading these you should understand that is not div+css is certainly good, the same page effect some web designers with only a few div can be easily implemented, and some web designers have to use more than the former twice times or even several times of code.

Div nesting div speed will be equally slow