Tags |
|
|
Links |
|
|
Will You Add? - 60 Performance and Optimization Tips for Your Website
So you have created a great website, your traffic is increasing each day, and you have began earning some money from those Adsense ads you strategically placed. Adsense is a great source for income but are you getting the most money out of those ads as you can? The answer may be no.Many of the top webmasters and marketers use a great tool that can be utilized when generating your Adsense codes. It is very simple to use but very few people actually utilize this feature, and the ones that are may not be using it correctly, which could be costing you with each visitor to your web page. The feature that I am referring to is the 'Alternate URL' option. If you are letting Google place Public Service Ads on your site then when there is no current relevant ads to show then only a PSA shows which you get no compensation for. These alternate ads only show up when Google has no ads to show that are relevant to the content on your site.The trick to using this feature effectively is to find an alternate site that pays a high click rate. There are several affiliate sites that have these codes set up and I have tried a few of them. Ther
39. Use quick page caching for pages that are displayed repeatedly (think auto-refresh): <%@ Page OutputCache VaryByParams="none" Duration="60" %>
40. If not using form post-back, turn off viewstate:
<%@ Page EnableViewState="false" %>
41. Avoid catching unnecessary exceptions: exceptions incur a large amount of overhead and should not be used for program logic flow control.
42. Avoid throwing exceptions.
43. Enable buffering.
44. Use Page.IsPostBack to prevent code from being needlessly executed.
45. Ensure debug is set to false and the release build is used in production.
46. Use client-side validation controls to reduce server round-trips.
47. Use StringBuilder when concatenating strings.
Database
48. Use SQL Server or another professional level database over Access.
49. Use stored procedures over simple SQL queries.
50. Connection Pooling – ensure connection pooling is enabled by using a DSN (Data Source Name) in the ODBC Data Source Administrator.
IIS
51. Use server side compression software such as Port80’s httpZip
(http://www.port80software.com/products/httpzip/)
52. Use GZip compression to reduce bandwidth, but be aware that CPU utilization may go up. A-B testing can help you find the right balance of whether GZip compression is right for your website.
53. Use IIS 6.0, which includes significant performance enhancements such as Kernel Caching.
54. Don’t install or use Microsoft Index Server unless you need it. The cost far outweighs the benefits that Index S
People are often confused when it comes to web analytics. They often ask why web analytics is important, and why they need to implement some kind of program. Some web hosting companies, and IT departments are able to offer basic statistics to marketing and sales if they ask for them, but the results are primative at best. Most clients who we speak with have no analytics in place at all, including many large corporations. When we ask them how they are tracking PPC or other online advertising they respond that they don't know how successful they are, and what the return on investment (ROI) is. Being able to track your advertising expense vs. what you're getting back with sales or goals. Google Analytics has a built in feature that allows you to tag banner ads for example, and then track them via the web interface, culling the numbers to see what your ROI is. Features like these are just one of over eighty features that google analytics offers; features that your web hosting company or IT department can't tell you.Being able to track why your sales, or leads, are increasing is critical to the success of any company doing business o
Sections
A. General
B. Images
C. HTML
D. ASP
E. ASP.NET
F. Database
G. IIS
General – Hardware and Monitoring
1. Host your website with a company known for performance. Check newsgroups and web host listing sites such as TopHosts (http://www.tophosts.com) for companies known for high performance. In a shared server environment (not dedicated hosting), find out how many other websites are on the same server as yours. Some web hosts will put up to 1 thousand sites on one server.
2. When hosting your own website, install as much physical RAM as possible on the web server. As memory gets cheaper and cheaper by the minute it is one of the most cost effective purchases an IT department can make.
3. When hosting your own website, use quality hardware – don’t try and save money when purchasing the hardware that will run one of your most valuable assets.
4. When hosting your own website, consider purchasing quality NIC cards which can offload and reduce CPU usage for networking.
5. Monitor your web pages for performance to make more informed decisions. End-to-end testing of your website, e.g. testing of multiple web pages on your website, is essential to understanding weak points and places for improvement.
Images
6. Reduce the size of images by reducing the number of colors. Optimize your images with online tools like GifWorks (http://www.gifworks.com).
7. Reduce the size of images by reducing its dimensions. Cropping images, also known as relevance-enhancing, can reduce size and also help focus the attention of the quick eye of the web surfer.
8. Use the jpg format for photos. Jpeg compression is known for its exceptional compression abilities with regard to photos. Many tools, such as ACDSee (http://www.acdsee.com/) can easily convert images from one format to another and allow you to set the compression level for jpeg images.
9. Reduce the total number of images on one page. Most web browsers download up to 4 images concurrently; however, each connection adds to the overall response/load time.
10. Reuse images whenever possible to take advantage of server-side (web server) and client-side (browser) caching.
11. Specify image WIDTH and HEIGHT attributes for faster loading in the browser.
12. Combine images and use image maps instead of segmenting images, remembering that each image loaded is a connection between the web browser and the web server.
13. Use image ALT attributes sparingly. Each character adds to the size of the web page and to the load time.
HTML
14. Use comments sparingly. While invisible when a web page is loaded in a browser, the comments are still transferred from the web server, needlessly wasting bandwidth.
15. Avoid unnecessary HTML tags: not all tags need a closing tag. For example, it is not necessary to have a close or tag.
16. Optimize your HTML code with free online tools such as iWebTool (http://www.iwebtool.com/html_optimizer) to reduce the overall size of the html file.
17. Avoid using frames. Each frame loads its own web page which can increase the overall response time of a webpage.
18. Minimize the amount of text and sub-tags between the HEAD open and close tag.
19. Place external JavaScript tags, i.e. with src=”[someurl]”, at the end of the document to delay loading.
20. Simplify tables and avoid nested tables (tables within tables).
21. In tables use background colors instead of images.
22. Avoid using WYSIWYG editors, e.g. FrontPage, that include extra and irrelevant text and HTML tags. Learn to edit HTML code by hand.
ASP
23. Disable Session State if not using sessions. If you are using sessions, consider using cookies or an id in the query string along with temporarily storing data in a database. To disable session state, at the top of your ASP page, include the directive:
<%@ ENABLESESSIONSTATE=false %>
24. Use Option Explicit to reduce coding errors. At the top of your ASP page, include the directive:
<% Option Explicit %>
25. Use Server.Transfer over Response.Redirect. Response.Redirect uses an additional round-trip to the web server whereas Server.Transfer does not, reducing the amount of bandwidth used, system resources, and overall response time.
26. When specifying a URL without a web page, e.g. http://www.exclamationsoft.com, include the trailing slash, e.g. http://www.exclamationsoft.com/, to save a trip back to the web server.
27. Reduce the use of global variables.
28. Reduce the number of include files used on a page. Also, segment and categorize functions in commonly used include files.
29. Be careful of string concatenation as the size of the string grows. As the string grows through concatenation, it is copied to a new location in memory each time.
30. Set objects, especially database objects to Nothing when no longer needed. For example, Set oRecordset = Nothing.
31. Keep blocks of ASP script together. Each switch between ASP script and HTML causes the compiler to stop and start processing.
32. Don’t use ASP commenting: <% ‘ comment %> which is compiled each time the page is loaded. Instead, use HTML commenting or no commenting at all.
33. Don’t leave empty Session_OnStart or Session_OnEnd methods. If Sessions are not used in your application, remove these two methods since they will be compiled and executed even when empty.
ASP.NET
34. ASP.NET Cache API. If you are not using the Cache API, stop your coding and read the help on this subject and implement it as soon as possible.
35. Reduce multiple database resultsets. Each database query with returned results is a round trip to the database server, adding to the overall response time.
36. Use “paged” data access, e.g. ASP.NET makes it easy to create DataGrids and DataLists of results from database queries. Use them to your advantage by only showing a small sub-set of those results to improve web page response times.
37. Use HttpContext.Items to add frequently used objects during a single page load to create a “per-request” cache.
38. Utilize background processing to help with long running tasks. Create multi-threaded operations when possible and feasible.
39. Use quick page caching for pages that are displayed repeatedly (think auto-refresh): <%@ Page OutputCache VaryByParams="none" Duration="60" %>
40. If not using form post-back, turn off viewstate:
<%@ Page EnableViewState="false" %>
41. Avoid catching unnecessary exceptions: exceptions incur a large amount of overhead and should not be used for program logic flow control.
42. Avoid throwing exceptions.
43. Enable buffering.
44. Use Page.IsPostBack to prevent code from being needlessly executed.
45. Ensure debug is set to false and the release build is used in production.
46. Use client-side validation controls to reduce server round-trips.
47. Use StringBuilder when concatenating strings.
Database
48. Use SQL Server or another professional level database over Access.
49. Use stored procedures over simple SQL queries.
50. Connection Pooling – ensure connection pooling is enabled by using a DSN (Data Source Name) in the ODBC Data Source Administrator.
IIS
51. Use server side compression software such as Port80’s httpZip
(http://www.port80software.com/products/httpzip/)
52. Use GZip compression to reduce bandwidth, but be aware that CPU utilization may go up. A-B testing can help you find the right balance of whether GZip compression is right for your website.
53. Use IIS 6.0, which includes significant performance enhancements such as Kernel Caching.
54. Don’t install or use Microsoft Index Server unless you need it. The cost far outweighs the benefits that Index S
Team Building Question:How do you treat team members who have reached the salary bar and cannot be promoted to the next level just yet? What do you do to keep them motivated?The Team Doc Says…This happens in many organizations due to the workforce getting older and maintaining a large number of veteran team members in the mix.Take the focus off money. It’s a motivator, but short term. Take a look at what the team member values and see what you can do to provide motivation to accommodate those values.One thing you can do right now is to understand how each team member perceives their fit in your organization. You can find out how your employees feel by asking them: What do you find most challenging about your work? What aspect of your work provides the most satisfaction? What are the biggest obstacles to completing your work? What resources would make your work easier? Finding the answers to these questions can help you in nailing down just the right motivational tactic to keep each team member on the right track. Then create action plans
7. Reduce the size of images by reducing its dimensions. Cropping images, also known as relevance-enhancing, can reduce size and also help focus the attention of the quick eye of the web surfer.
8. Use the jpg format for photos. Jpeg compression is known for its exceptional compression abilities with regard to photos. Many tools, such as ACDSee (http://www.acdsee.com/) can easily convert images from one format to another and allow you to set the compression level for jpeg images.
9. Reduce the total number of images on one page. Most web browsers download up to 4 images concurrently; however, each connection adds to the overall response/load time.
10. Reuse images whenever possible to take advantage of server-side (web server) and client-side (browser) caching.
11. Specify image WIDTH and HEIGHT attributes for faster loading in the browser.
12. Combine images and use image maps instead of segmenting images, remembering that each image loaded is a connection between the web browser and the web server.
13. Use image ALT attributes sparingly. Each character adds to the size of the web page and to the load time.
HTML
14. Use comments sparingly. While invisible when a web page is loaded in a browser, the comments are still transferred from the web server, needlessly wasting bandwidth.
15. Avoid unnecessary HTML tags: not all tags need a closing tag. For example, it is not necessary to have a close or tag.
16. Optimize your HTML code with free online tools such as iWebTool (http://www.iwebtool.com/html_optimizer) to reduce the overall size of the html file.
17. Avoid using frames. Each frame loads its own web page which can increase the overall response time of a webpage.
18. Minimize the amount of text and sub-tags between the HEAD open and close tag.
19. Place external JavaScript tags, i.e. with src=”[someurl]”, at the end of the document to delay loading.
20. Simplify tables and avoid nested tables (tables within tables).
21. In tables use background colors instead of images.
22. Avoid using WYSIWYG editors, e.g. FrontPage, that include extra and irrelevant text and HTML tags. Learn to edit HTML code by hand.
ASP
23. Disable Session State if not using sessions. If you are using sessions, consider using cookies or an id in the query string along with temporarily storing data in a database. To disable session state, at the top of your ASP page, include the directive:
<%@ ENABLESESSIONSTATE=false %>
24. Use Option Explicit to reduce coding errors. At the top of your ASP page, include the directive:
<% Option Explicit %>
25. Use Server.Transfer over Response.Redirect. Response.Redirect uses an additional round-trip to the web server whereas Server.Transfer does not, reducing the amount of bandwidth used, system resources, and overall response time.
26. When specifying a URL without a web page, e.g. http://www.exclamationsoft.com, include the trailing slash, e.g. http://www.exclamationsoft.com/, to save a trip back to the web server.
27. Reduce the use of global variables.
28. Reduce the number of include files used on a page. Also, segment and categorize functions in commonly used include files.
29. Be careful of string concatenation as the size of the string grows. As the string grows through concatenation, it is copied to a new location in memory each time.
30. Set objects, especially database objects to Nothing when no longer needed. For example, Set oRecordset = Nothing.
31. Keep blocks of ASP script together. Each switch between ASP script and HTML causes the compiler to stop and start processing.
32. Don’t use ASP commenting: <% ‘ comment %> which is compiled each time the page is loaded. Instead, use HTML commenting or no commenting at all.
33. Don’t leave empty Session_OnStart or Session_OnEnd methods. If Sessions are not used in your application, remove these two methods since they will be compiled and executed even when empty.
ASP.NET
34. ASP.NET Cache API. If you are not using the Cache API, stop your coding and read the help on this subject and implement it as soon as possible.
35. Reduce multiple database resultsets. Each database query with returned results is a round trip to the database server, adding to the overall response time.
36. Use “paged” data access, e.g. ASP.NET makes it easy to create DataGrids and DataLists of results from database queries. Use them to your advantage by only showing a small sub-set of those results to improve web page response times.
37. Use HttpContext.Items to add frequently used objects during a single page load to create a “per-request” cache.
38. Utilize background processing to help with long running tasks. Create multi-threaded operations when possible and feasible.
39. Use quick page caching for pages that are displayed repeatedly (think auto-refresh): <%@ Page OutputCache VaryByParams="none" Duration="60" %>
40. If not using form post-back, turn off viewstate:
<%@ Page EnableViewState="false" %>
41. Avoid catching unnecessary exceptions: exceptions incur a large amount of overhead and should not be used for program logic flow control.
42. Avoid throwing exceptions.
43. Enable buffering.
44. Use Page.IsPostBack to prevent code from being needlessly executed.
45. Ensure debug is set to false and the release build is used in production.
46. Use client-side validation controls to reduce server round-trips.
47. Use StringBuilder when concatenating strings.
Database
48. Use SQL Server or another professional level database over Access.
49. Use stored procedures over simple SQL queries.
50. Connection Pooling – ensure connection pooling is enabled by using a DSN (Data Source Name) in the ODBC Data Source Administrator.
IIS
51. Use server side compression software such as Port80’s httpZip
(http://www.port80software.com/products/httpzip/)
52. Use GZip compression to reduce bandwidth, but be aware that CPU utilization may go up. A-B testing can help you find the right balance of whether GZip compression is right for your website.
53. Use IIS 6.0, which includes significant performance enhancements such as Kernel Caching.
54. Don’t install or use Microsoft Index Server unless you need it. The cost far outweighs the benefits that Index S
Career Counselors“Understand that career counselors and recruiters offer two different services”Career counselors / coaches offer one on one session’s. They help answer the clients many questions of “How to make a successful career transition.” When you have been networking, answering ads, meeting with support groups but are not getting results than you might think about seeing a career counselor / coach. They can help you identify why or what pieces you are missing to get lasting results. Typically recruiters look for the degree and the list of your skills in order to get you in front of the decision maker for an interview. However recruiters often don’t have the skills to help clients transition into new or different careers, ace and prep you for the interview, or negotiate the best offer. I’ve listed more below about what to look for when you use a recruiter. Here are four clear differences that career counselors / coaches provide that typically recruiters do not.1. Career counselors provide a holistic approach to measure the correct career fit 2. Career counselo
17. Avoid using frames. Each frame loads its own web page which can increase the overall response time of a webpage.
18. Minimize the amount of text and sub-tags between the HEAD open and close tag.
19. Place external JavaScript tags, i.e. with src=”[someurl]”, at the end of the document to delay loading.
20. Simplify tables and avoid nested tables (tables within tables).
21. In tables use background colors instead of images.
22. Avoid using WYSIWYG editors, e.g. FrontPage, that include extra and irrelevant text and HTML tags. Learn to edit HTML code by hand.
ASP
23. Disable Session State if not using sessions. If you are using sessions, consider using cookies or an id in the query string along with temporarily storing data in a database. To disable session state, at the top of your ASP page, include the directive:
<%@ ENABLESESSIONSTATE=false %>
24. Use Option Explicit to reduce coding errors. At the top of your ASP page, include the directive:
<% Option Explicit %>
25. Use Server.Transfer over Response.Redirect. Response.Redirect uses an additional round-trip to the web server whereas Server.Transfer does not, reducing the amount of bandwidth used, system resources, and overall response time.
26. When specifying a URL without a web page, e.g. http://www.exclamationsoft.com, include the trailing slash, e.g. http://www.exclamationsoft.com/, to save a trip back to the web server.
27. Reduce the use of global variables.
28. Reduce the number of include files used on a page. Also, segment and categorize functions in commonly used include files.
29. Be careful of string concatenation as the size of the string grows. As the string grows through concatenation, it is copied to a new location in memory each time.
30. Set objects, especially database objects to Nothing when no longer needed. For example, Set oRecordset = Nothing.
31. Keep blocks of ASP script together. Each switch between ASP script and HTML causes the compiler to stop and start processing.
32. Don’t use ASP commenting: <% ‘ comment %> which is compiled each time the page is loaded. Instead, use HTML commenting or no commenting at all.
33. Don’t leave empty Session_OnStart or Session_OnEnd methods. If Sessions are not used in your application, remove these two methods since they will be compiled and executed even when empty.
ASP.NET
34. ASP.NET Cache API. If you are not using the Cache API, stop your coding and read the help on this subject and implement it as soon as possible.
35. Reduce multiple database resultsets. Each database query with returned results is a round trip to the database server, adding to the overall response time.
36. Use “paged” data access, e.g. ASP.NET makes it easy to create DataGrids and DataLists of results from database queries. Use them to your advantage by only showing a small sub-set of those results to improve web page response times.
37. Use HttpContext.Items to add frequently used objects during a single page load to create a “per-request” cache.
38. Utilize background processing to help with long running tasks. Create multi-threaded operations when possible and feasible.
39. Use quick page caching for pages that are displayed repeatedly (think auto-refresh): <%@ Page OutputCache VaryByParams="none" Duration="60" %>
40. If not using form post-back, turn off viewstate:
<%@ Page EnableViewState="false" %>
41. Avoid catching unnecessary exceptions: exceptions incur a large amount of overhead and should not be used for program logic flow control.
42. Avoid throwing exceptions.
43. Enable buffering.
44. Use Page.IsPostBack to prevent code from being needlessly executed.
45. Ensure debug is set to false and the release build is used in production.
46. Use client-side validation controls to reduce server round-trips.
47. Use StringBuilder when concatenating strings.
Database
48. Use SQL Server or another professional level database over Access.
49. Use stored procedures over simple SQL queries.
50. Connection Pooling – ensure connection pooling is enabled by using a DSN (Data Source Name) in the ODBC Data Source Administrator.
IIS
51. Use server side compression software such as Port80’s httpZip
(http://www.port80software.com/products/httpzip/)
52. Use GZip compression to reduce bandwidth, but be aware that CPU utilization may go up. A-B testing can help you find the right balance of whether GZip compression is right for your website.
53. Use IIS 6.0, which includes significant performance enhancements such as Kernel Caching.
54. Don’t install or use Microsoft Index Server unless you need it. The cost far outweighs the benefits that Index S
None of these Government Grants require a credit check, collateral, security deposits or co-signers, you can apply even if you have a bankruptcy or bad credit, it doesn't matter. Its Free Money Never Repay!The Federal Government is Giving out over 155.5 billion dollars in Business Grants!Receive Government Small Business Grants for virtually any type of business. Whether it is to start a business or expand your existing business there is money for waiting just for you. The Federal government provides this money to help existing small business owners and those who want to start their own business change their lives and achieve financial independence.The United States Government wants your Small Business to succeed and you will be amazed at the lengths they will go to help ensure your success. At Grant Seeker Pro™ we have designed a State of the art software program that will aid you in locating the perfect grant or grants for your small business!Once you find the programs for Small Business Grants that fit your needs you can use the Grant Seeker Pro™ software program to complete the applications! Don't forget
29. Be careful of string concatenation as the size of the string grows. As the string grows through concatenation, it is copied to a new location in memory each time.
30. Set objects, especially database objects to Nothing when no longer needed. For example, Set oRecordset = Nothing.
31. Keep blocks of ASP script together. Each switch between ASP script and HTML causes the compiler to stop and start processing.
32. Don’t use ASP commenting: <% ‘ comment %> which is compiled each time the page is loaded. Instead, use HTML commenting or no commenting at all.
33. Don’t leave empty Session_OnStart or Session_OnEnd methods. If Sessions are not used in your application, remove these two methods since they will be compiled and executed even when empty.
ASP.NET
34. ASP.NET Cache API. If you are not using the Cache API, stop your coding and read the help on this subject and implement it as soon as possible.
35. Reduce multiple database resultsets. Each database query with returned results is a round trip to the database server, adding to the overall response time.
36. Use “paged” data access, e.g. ASP.NET makes it easy to create DataGrids and DataLists of results from database queries. Use them to your advantage by only showing a small sub-set of those results to improve web page response times.
37. Use HttpContext.Items to add frequently used objects during a single page load to create a “per-request” cache.
38. Utilize background processing to help with long running tasks. Create multi-threaded operations when possible and feasible.
39. Use quick page caching for pages that are displayed repeatedly (think auto-refresh): <%@ Page OutputCache VaryByParams="none" Duration="60" %>
40. If not using form post-back, turn off viewstate:
<%@ Page EnableViewState="false" %>
41. Avoid catching unnecessary exceptions: exceptions incur a large amount of overhead and should not be used for program logic flow control.
42. Avoid throwing exceptions.
43. Enable buffering.
44. Use Page.IsPostBack to prevent code from being needlessly executed.
45. Ensure debug is set to false and the release build is used in production.
46. Use client-side validation controls to reduce server round-trips.
47. Use StringBuilder when concatenating strings.
Database
48. Use SQL Server or another professional level database over Access.
49. Use stored procedures over simple SQL queries.
50. Connection Pooling – ensure connection pooling is enabled by using a DSN (Data Source Name) in the ODBC Data Source Administrator.
IIS
51. Use server side compression software such as Port80’s httpZip
(http://www.port80software.com/products/httpzip/)
52. Use GZip compression to reduce bandwidth, but be aware that CPU utilization may go up. A-B testing can help you find the right balance of whether GZip compression is right for your website.
53. Use IIS 6.0, which includes significant performance enhancements such as Kernel Caching.
54. Don’t install or use Microsoft Index Server unless you need it. The cost far outweighs the benefits that Index S
Is it really possible? Of course it is and any one that can turn a computer on can do it. It takes some perseverance and investment along the way to get started, but within a short amount time you can make money with your computer from the comfort of your home.Let's face it we could all use more money right? To pay off the car, house or to just have that financial security that so many people long for. Who could blame you for wanting to leave the 9 to 5 grind behind and actually slow down and enjoy life. I have been there myself and I took the next step and I'll never look back.Do not for a second think to yourself that you cannot make money with your computer. If you can turn the dang thing on, than you have what it takes. I am not kidding you, people from all walks of life have come online in search of financial freedom and hit it big time within a year of doing so.All it takes is action on your part. That is the first and hardest part is to get started. Once you have started things just start falling into place. Please do not for a second think that there is not a learning curve to make money online, because th
39. Use quick page caching for pages that are displayed repeatedly (think auto-refresh): <%@ Page OutputCache VaryByParams="none" Duration="60" %>
40. If not using form post-back, turn off viewstate:
<%@ Page EnableViewState="false" %>
41. Avoid catching unnecessary exceptions: exceptions incur a large amount of overhead and should not be used for program logic flow control.
42. Avoid throwing exceptions.
43. Enable buffering.
44. Use Page.IsPostBack to prevent code from being needlessly executed.
45. Ensure debug is set to false and the release build is used in production.
46. Use client-side validation controls to reduce server round-trips.
47. Use StringBuilder when concatenating strings.
Database
48. Use SQL Server or another professional level database over Access.
49. Use stored procedures over simple SQL queries.
50. Connection Pooling – ensure connection pooling is enabled by using a DSN (Data Source Name) in the ODBC Data Source Administrator.
IIS
51. Use server side compression software such as Port80’s httpZip
(http://www.port80software.com/products/httpzip/)
52. Use GZip compression to reduce bandwidth, but be aware that CPU utilization may go up. A-B testing can help you find the right balance of whether GZip compression is right for your website.
53. Use IIS 6.0, which includes significant performance enhancements such as Kernel Caching.
54. Don’t install or use Microsoft Index Server unless you need it. The cost far outweighs the benefits that Index Server will give.
55. Don’t enable logging unless needed. Logging is disk and resource intensive.
56. Run IIS “in-process” if the website is mostly static. Mostly dynamic or unstable websites should not use this setting.
57. Enable “Cache ISAPI applications” for sites that use ASP which benefits greatly from this setting.
58. Disable debugging on production servers.
59. Enable “HTTP Keep Alives” for IIS 5.0 – This setting is enabled by default in IIS 6.0.
60. Shorten connection timeouts to reduce the hold on resources.
Resources used:
1. MSDN
2. Chapter 6 — Improving ASP.NET Performance
3. Tips to Improve ASP Application Performance
4. IIS 101: The Basics of Performance Tuning
5. Top Ten Ways To Pump Up IIS Performance
Copyright 2006 ExclamationSoft
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.atriclecheck.com/article/86790/atriclecheck-60-Performance-and-Optimization-Tips-for-Your-Website.html">60 Performance and Optimization Tips for Your Website</a>
BB link (for phorums):
[url=http://www.atriclecheck.com/article/86790/atriclecheck-60-Performance-and-Optimization-Tips-for-Your-Website.html]60 Performance and Optimization Tips for Your Website[/url]
Related Articles:
Medical Billing - Hiring A Staff
Entrepreneurship as a Career Choice?
What Does the Public Relations Client REALLY Want, and Why?
Bookmark it:
|