blocks|key|2520471|text|这是一个很好的工具，用来找出网页的速度，并告诉你是什么让它变慢的：https://developers.google.com/speed/pagespeed/insights|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2520472|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/speed/pagespeed/insights^0|X|1I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This is a great tool to find the speed of web pages and tells you what makes it slow: <a href="https://developers.google.com/speed/pagespeed/insights" rel="noreferrer">https://developers.google.com/speed/pagespeed/insights</a>

blocks|key|2520499|text|通常情况下，用户会以页面加载时间作为衡量标准，以确定站点是否运行缓慢。但是如果你真的想知道最长的时间是什么，你可以通过按f12打开浏览器调试器。如果你的浏览器是chrome，点击network，看看你的应用程序正在进行什么调用，哪些调用占用了最多的时间。如果你使用的是Firefox，你需要安装firebug。如果有，请再次按f12键并单击Net。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2520500|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Normally the user takes the page loading time as a measure to find out that the site is slow. But if you really want to know that what is taking the maximum time the you can open the browser debugger by pressing f12. if your browser is chrome the click on network and see what calls your application is making and which are taking maximum time. If you are using Firefox the you need to install firebug. If you have that, then again press f12 and click on Net.

blocks|key|2520556|text|因为您已经说过，当您自己检查站点时，速度很好，这意味着(至少对于您检查的页面)服务器没有任何问题，它可以以良好的速度为这些页面提供服务。在这一点上，你应该弄清楚的是，你和报告你的网站速度慢的用户之间的区别是什么。可能有很多不同的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2520557|2520558|用户是否使用慢速网络连接(例如移动设备)？|unordered-list-item|2520559|用户是否遇到与同一网站托管中心托管的其他网站相同的问题？如果是这样，这可能表示存在网络问题。通常情况下，这也可能表示and服务器上的资源有问题，但在这种情况下，站点的运行速度也会很慢。|2520560|如果以上两种情况都不能给出答案，则可以假定到服务器的连接和服务器本身都是正常的。这意味着问题一定出在用户设备上。找出他使用的浏览器/操作系统，并尝试重现该问题。如果失败，找出他是否使用了任何可能导致问题的杀毒软件或类似软件。|2520561|2520562|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

Since you already said when you check the site yourself the speed is fine, this means that (at least for the pages you checked) there is nothing wrong with the server and it can serve those pages at a good speed. What you should be figuring out at this point is what the difference is between you and the user that reports your site is slow. It might be a lot of different things:

<ul>
<li>Is the user using a slow network connection (mobile for example)?</li>
<li>Does the user experience the same problems with other websites hosted at the same webhoster? If so, this could indicate a network problem. Normally this could also indicate a resource problem at the webserver, but in that case the site would also be slow for you.</li>
<li>If neither of the above leads to an answer, you could assume that the connection to the server and the server itself are fine. This means the problem must be in the users device. Find out which browser/OS he uses and try to replicate the problem. If that fails find out if he uses any antivirus or similar software that might cause problems.</li>
</ul>

blocks|key|44379|text|一个原因可能是用户的角色与您的角色不同。您可能拥有管理员权限(例如超级用户角色)，而代码可能只是允许此类角色的所有内容，这意味着它实际上不会执行太多的条件检查来查看允许或不允许的内容。有时，获取用户的所有特权并检查条件是相当困难的，过程如何取决于如何实现授权。这意味着，对于特定的角色，页面可能会非常慢。因此，您应该找出用户的角色，并查看这是否是原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|44380|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One reason could be the role of the user is different of your role. You might be having suppose an administrator privilege (some thing like super user role) and the code might be just allowing everything for such role that means it does not really do much of conditional checking to see what is allowed or not. Some times, it's a considerable over ahead to get all the privileges of the user and have the conditions checking, how course depends how how the authorization is implemented. That means, the page might be really slow for specific roles. Hence, you should find out the roles of the user and see if that is a reason.

blocks|key|44382|text|很明显，连接到你的站点的人的连接出现了问题，或者这可能是一个暂时的问题，当你检查你的站点时，一切都很好。您可以检查您的日志或询问您的主机在发生减速时是否存在问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|44383|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Obviously an issue with the connection of the person connecting to your site OR it's possible it was a temporary issue and by the time you checked your site, everything was dandy. You could check your logs or ask your host if there was an issue at the time the slow down occured.

blocks|key|2520642|text|这通常是一个内存问题，可以通过增加托管应用程序的Web服务器的堆大小来解决。如果应用程序在Weblogic+Server上运行。堆大小可以在位于应用程序主页的"setEnv“文件中增加。祝你好运！迈克尔·奥雷贝|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2520643|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This is usually a memory issue and it can be resolved by increasing the Heap Size of the Web Server hosting the application. In case the application is running on Weblogic Server. Heap size can be increased in "setEnv" file located in Application Home.
Goodluck!
Michael Orebe

blocks|key|44458|text|我认为上述答案中缺少的一个重要因素是服务器位置，这对web性能起着至关重要的作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|44459|当有人说打开网页需要更长的时间时，这意味着很高的延迟。由于服务器位置的原因，可能会导致高延迟。让我们假设您是web页面的所有者，那么服务器和客户端位于同一位置，因此它将具有低延迟。|44460|但是，现在如果客户端跨越边界，那么延迟时间将急剧增加。也因此表现缓慢。|44461|另一个因素是缓存，它极大地影响了延迟时间。|44462|以facebook为例，他们在世界各地都有服务器来减少延迟时间(还提供了其他几个优势)，他们使用巨大的缓存系统来缓存他们的热门数据(热门话题)，而冷数据(旧数据)存储在硬盘中，因此加载旧照片或帖子需要更长的时间。因此，用户在尝试加载一些冷数据时可能会抱怨这一点。|44463|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I think one of the important thing that is missing from above answers is the server location, which can play a vital in web performance.

When someone is saying that it is taking a longer time to open a web page that means high latency. High latency can be caused due to server location. 
Let's assume as you are the owner of the web page then the server and client are co-located, so it will have a low latency.

But, now if client is across the border, then latency time will increase drastically. And hence a slow perfomance.

Another factor is caching which drastically affects the latency time.

Taking the example of facebook, they have server all over the world to reduce the latency time (and also to provide several other advantages) and they use huge caching system to cache their hot data (trending topics) whereas cold data (old data) are stored in hard disk so it takes a longer time to load an older photo or post.
So, a user might would have complained about this as they were trying load up some cold data.

blocks|key|44577|text|我可以想到以下几个原因(前面已经提到过前两个原因)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|44578|由于客户端位置的原因，|44579|高延迟|ordered-list-item|44580|服务器内存可能需要是来自页面的服务调用的increased|44581|Number。|44582|如果某个服务在收到投诉时可能会关闭，则可能会阻止页面加载。|44583|在体验不佳时，服务器负载可能过高。服务器可能需要增加资源(例如，向集群中添加另一个服务器/web服务器)。|44584|检查当时服务器上是否正在运行任何后台作业。|44585|44586|检查批处理作业的日志和计划非常重要，以确定当时所有作业都在运行什么。|44587|希望这能有所帮助。|44588|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|W|$]]

I can think of these few reasons (first two are already mentioned above): 

<ol>
<li>High Latency due to location of client</li>
<li>Server memory might need to be increased</li>
<li>Number of service calls from the page. </li>
<li>If a service could be down at the time of complaint, it could prevent page from loading.</li>
<li>The server load might be too high at the time of the poor experience. The server might need to increase the resources (e.g. adding another server/web server to the cluster). </li>
<li>Check if there was any background job running on the server at that time. </li>
</ol>

It is important to check the logs and schedules of the batch jobs to determine what all was running at that time. 

Hope this help.

blocks|key|44615|text|虽然你的问题很清楚，但网站优化是一个非常广泛的主题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|44616|由于某些原因，大多数流行的web开发框架都是处理器效率极低的。|44617|根据W3C的说法，开发n层web应用程序的老式方法仍然非常相关，并且仍然被认为是最佳实践。如果你花一点时间阅读最流行的web开发框架的源代码结构，你会发现它们在服务器上运行的代码比必要的要多得多。|44618|这可能看起来有点简单，但是，在服务器上运行的代码越少，在客户端运行的代码越多，服务器的运行速度就会越快。有时，将框架代码与传统方式进行对比是理解这一点的最好方法。这是一个完全工作的迷你web应用程序的链接，它代表了W3C的最佳实践，在服务器上运行最少的代码，在客户端运行最大数量的代码：http://developersfound.com/W3C_MVC_EX.zip这个代码库也是MVC兼容的。|offset|length|44619|这个代码库附带了MySQL数据库转储、php和客户端代码。要查看这些代码的实际效果，您需要将SQL+dump恢复到MySQL实例(sql+dump来自MySQL+8社区)，并添加在php文件(conn_include.php)中找到的用户和模式权限；将用户设置为对模式具有execute权限。|44620|如果你将这个代码库与所有最流行的web框架进行对比，你会发现这些框架是多么的低效。声称是MVC框架的流行PHP框架实际上根本不兼容MVC。这是因为它们依赖于在HTML标签中嵌入PHP标签，或者相反(根据W3C，这被认为是非常糟糕的做法)。而且，大多数流行的节点框架在服务器上运行的代码远远多于所需的代码。嵌入的标记也会阻止异步调用正常工作，除非框架支持AJAX转储，比如Yii+2。|44621|遵循MVC的两个最重要的规则是:永远不要在HTML标记中嵌入服务器端标记(比如PHP标记)，或者反之亦然(除非有一个非常好的借口，比如SEO)，并且如果代码可以在客户端运行，就绝对不要编写代码在服务器端运行。同样，真正的MVC是基于层分离的，而MVC框架是基于代码分离的。真正的MVC兼容是非常高效的处理器。不要误会我的意思，MVC框架在很多事情上都非常有用，但是如果你正在开发一个点击率将达到数百万的网站，它们是完全没有用的，或者至少它们会把你的云账单推得如此之高，以至于它真的会侵蚀你公司的利润。|44622|总而言之，框架不能很好地控制在客户端或服务器上运行的代码，而且效率非常低，但您可以用更少的代码更快地启动和运行原型。|44623|相比之下，老式的方法需要更多的体力，但您可以完全控制在服务器上运行的内容和在客户端运行的内容。|44624|作为额外的优化建议，请避免使用直通查询和触发器，而应选择存储过程。从历史上看，存储过程并不是在MVC作为一种范式出现的时候发明的，但它无疑增加了各层之间的关注点分离，并且处理器效率更高。|44625|希望这个建议能有所帮助。|44626|entityMap|0|LINK|mutability|MUTABLE|url|http://developersfound.com/W3C_MVC_EX.zip^0|0|0|0|3Z|15|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@$H|19|I|1A|1|1B]]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1H|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1I|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]]]

Though your question is quite clear, web site optimisation is a very extensive subject.

The majority of the popular web developing frameworks are for some reason, extremely processor inefficient.

The old fashioned way of developing n-tier web applications is still very relevant and is still considered to be best practice according the W3C. If you take a little time to read the source code structure of the most popular web developing frameworks you will see that they run much more code at the server than is necessary.

This may seem a bit of a simple answer but, the less code you run at the server and the more code you run at the client the faster your servers will work.
Sometimes contrasting framework code against the old fashioned way is the best way to get an understanding of this. Here is a link to a fully working mini web application which represents W3C best practices and runs the minimum amount of code at the server and the maximum amount of code at the client: <a href="http://developersfound.com/W3C_MVC_EX.zip" rel="nofollow noreferrer">http://developersfound.com/W3C_MVC_EX.zip</a> this codebases is also MVC compliant.

This codebase comes with a MySQL database dump, php and client side code. To see this code in action you will need to restore the SQL dump to a MySQL instance (sql dump came from MySQL 8 Community) and add the user and schema permissions that are found in the php file (conn_include.php); setting the user to have execute permissions on the schema.

If you contrast this code base against all of the most popular web frameworks, it will really open your eyes to just how inefficient these frameworks are. The popular PHP frameworks that claim to be MVC frameworks aren’t actually MVC compliant at all. This is because they rely on embedding PHP tags inside HTML tags or visa-versa (considered very bad practice according the W3C). Also most popular node frameworks run way more code at the server than is necessary. Embedded tags also stop asynchronous calls from working properly unless the framework supports AJAX dumps such as Yii 2.

Two of the most important rules to follow with MVC compliance is: never embed server side tags (such as PHP tags) in HTML tags or visa-versa (unless there is a very good excuse such as SEO) and religiously never write code to run at the server if it can be run at the client. Also true MVC is based on tier separation, where as the MVC frameworks are based on code separation. True MVC compliance is very processor efficient. Don’t get me wrong MVC frameworks are very useful for a lot of things, but if you’re developing a site that is going to get millions of hits, they are quite useless, or at least they will drive your cloud bills so high that it will really eat into your company’s profits.

In summary frameworks don’t give much control over what code runs at the client or server and are very inefficient but you can get prototypes up and running quicker with less code.

In contrast the old fashioned way takes a bit more elbow grease but you have complete control over what runs at the server and what runs at the client.

As an additional bit of advice for optimisation avoid using pass-through queries and triggers and instead opt for stored procedures. Historically stored procedures weren’t invented at the time MVC was present as a paradigm but it definitely increases separation of concerns between the tiers and is much more processor efficient.

Hope this advice helps.

I was asked this question once at an interview:

"Suppose you own a website where the server is at some remote location. One day, some user calls/emails you saying the site is abominably slow. How would you identify why the site is slow? Also, when you check the website yourself as any user would (using your browser), the site behaves just fine."

I could think of only one thing (which was shot down):

<ul>
<li>Check the server logs to analyse incoming traffic. Maybe a DoS attack or exceptionally high traffic. Interviewer told me to assume the server has normal traffic and no DoS.</li>
</ul>

I was kind of lost because I had never thought of this problem. I have almost no idea how running a server/website works. So if someone could highlight a few approaches, it would be nice.

While googling around, I could find <a href="http://samsaffron.com/archive/2011/05/02/A+day+in+the+life+of+a+slow+page+at+Stack+Overflow#" rel="noreferrer">only this relevant, wonderful article</a>. That article is kind of too technical for me now, but I'm slowly breaking it down and understanding it.

how does one identify why a website is slow?

SQL数据库

数据库

服务器

调试器

MySQL

在一次面试中，我被问到这个问题：“假设你有一个网站，服务器在某个远程位置。有一天，一些用户给你打电话/发电子邮件，说这个网站慢得令人讨厌。你如何确定网站慢的原因?而且，当你像任何用户一样(使用你的浏览器)自己检查网站时，网站运行正常。”我只能想到一件事(被击落)：检查服务器日志以分析传入流量。可能是DoS攻击，也可能是...

问如何识别网站运行缓慢的原因？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何识别网站运行缓慢的原因？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何识别网站运行缓慢的原因？
EN