Who in the dispute of the rights of the SEOs or the programmer?

Then puzzled question to the chief.
Programmer comments the code, and remove it with a goal in the future to look for bugs. In addition, uses the styles in the page body, and not stand in a separate css file for each page, according to Google recommendations speedtest.
SEOs says that code should be as short as possible in the body of the page and the unused code should be removed, and styles to make one common file of styles.
What do you think - is better and how allowed?
June 8th 19 at 17:01
7 answers
June 8th 19 at 17:03
If he then says in khtml it asshole
About in styles in the page there is a standard recommendation that waste should be much less content if proper all pulling in the page itself he's also an asshole, as it reduces the loading speed of the website
June 8th 19 at 17:05
Programmer comments the code instead of deleting it

Code in HTML? Or on the server side in PHP? If the first then Yes it is better to remove for speed download the same, if the latter do not matter to the user it does not reach.

styles to make a single shared file of the styles

here the programmer is right, the code should be left in the style tag in the header
php. - Nedra3 commented on June 8th 19 at 17:08
then the SEOs in General should not care what is there if it is in the code page does not appear, the php runs on the server before the page appears in the browser - Abdullah commented on June 8th 19 at 17:11
June 8th 19 at 17:07
Usually the code goes into production in the form in which the programmer writes, and is going with some build systems (webpack, gulp, etc.) where many of the files going into one, translirovatsya in a more supported language (js, css), minicircuits. The output, of course, all comments and unused code branches are removed. This compressed version and is used on the website, and in the development of used source from where the hands do not removed,
June 8th 19 at 17:09
Programmer comments the code instead of deleting it

Where? It is the cornerstone. On a production should only get clean code. But if it is dev part of the project, may comment. If it is not a minified js or even php, thanks to him I must say for the comments. I understand someone or all parties to the dispute have not heard anything about gulp, and this would solve the problem.

In addition, uses the styles in the page body, and not stand in a separate css file

Depends how many and are they used again. You've got to look at a specific example. To make a separate file for 10 lines of code and for this to make a separate request to the server, too bad.

SEOs says that code should be as short as possible in the page body and all unused code need to remove

then I'd break into two parts
- unused code should be removed - as if by itself of course
code must be as short as possible in the body of the page - what's this?
June 8th 19 at 17:11
Easy automatically clean up comments.
At least in the web server, before return to the client.
Even before when deploying to the server.

And CSS - Yes, should be separate.
And what secret sense?
I think if the css used throughout the site, the type of footers and headers, Yes. If a particular page, don't see much value - Nedra3 commented on June 8th 19 at 17:14
for each page - specific CSS in large amounts is rare.
The fact of the matter is that as a CSS rule in common.

Google Recommendations. Let's say for a "radically accelerated mobile pages" - there there is generally strictly forbidden CSS inside HTML - Abdullah commented on June 8th 19 at 17:17
June 8th 19 at 17:13
1. If makes in comments small areas of HTML that may be needed in the future, then that's fine.

2. Blame the CSS in the page body is not good. With the exception of styles that come in one block of <style></style>. It is necessary for PageSpeed.

3. Professional SEOs are little, they regard search engines as a deity, and are afraid once again to sneeze vyplyasyvaya with a tambourine, although their behavior 99% is subordinated to the logic. High speed page load, preferably a valid code and semantic coding. For example, it would be good to check that Gzip compression is configured, not to save every bytes.
June 8th 19 at 17:15
You can also comment on areas close tags, noindex so the search engine is not seen and all the problem is solved, but at the expense of speed, it is hardly commented code in thousands of lines, an extra hundred lines of text just won't do in terms of speed

Find more questions by tags Search engine optimization