Hi,
My Site is running very smooth and on normal speed, except one page, I am using IZAP Video latest version. When I Click on videos it open a list of videos but when I click on any video it take approx. 10-12 sec to open that and sometimes even more. Any other links are responding within a sec.
I am on dedicated server so there is no issue with server because all site is reponding very fast. One more thing when no user is online I tried to open a video that time when I click on video link then it says waiting for response and there was no load on server afer 7-8 second processor show some activity and then within few seconds page is open. This problem is start from few weeks ago before that everything was fine on same server.
I am trying to fix this issue from last week but no success. You can check that on.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
May be it's an Izap issue. It shouldn't give you problems if you are on a dedicated server.
Rodolfo Hernandez
Arvixe/Elgg Community Liaison
Thanks for your reply, Except Izap video play page I have no issue with performance. I tried lot of things to fix this before that I was on shared hosting and there it was slow but not like this time.
According to me I feel there is a loop whole in Izap or issue with rendering url to video , or any connectivity issue?
What version of izap_videos are you using?
As far as I know the latest versions (i.e. > 3.71) are depending on an external server at least for embedding videos. Maybe izap_videos is "calling home" each time when loading any video page? I remember something about the izap_videos server that's used for this service switched to another hoster not long ago. Maybe this server switch happened at the same time you started to notice the delay...
I am using latest version 3.9b before that I was on 3.8b this problem was from 3.8b then I try to go with latest one with issue will not resolved. So right now I am on latest one. I am only adding videos from youtube with URL . I disabled a option for embed video.
I is like a gap between a connection , look like trying to find something but not found and after 12-14 sec it open the page immediately, and I already monitor the processes on server which are showing activity only during last 1 or 2 sec before that there is no activity on server. May be some person from Izap team will asnwer my question correctly. I already post this issue on plugin lotto.
"Add URL" for example for Youtube videos is also kind of embedding a video. I guess izap_videos just adds the embed code for the provided URL internally. The question is if the API server provided by Izap is only used when adding the video or called each time the video page is loaded - the latter would surely be not the best solution.
I'm still on 3.71 as this version works without the API server and I don't notice such a delay.
I just tried yr site and grabbed a video to allow it to play. The browser sits waiting for the server. I think you may have some server configuration issues in the way it serves the video - which are most likely larger files and so the browser does not start to render until it has finished receiving that large file completely. Seen something like this happen on another site months ago. it was something to do with not 'chunking' the data, not gzipping or whatever something.. Try running LiveHtttp logging from FireFox to trace request and reply times (I used SeaMonkey and do not want to fire up FIreFox b/c FF spits too many memory leaks too quickly for my liking)
Thanks Dhrup, looks like a same thing you mention , I am going to rebuild the whole server this night , I am trying to monitor it from few days but get same result as you said some short videos open quickly in 3-4 sec.
First of all going to check with SeaMonkey if that works, befoer few days ago the 40 minutes video was open with few sec like 2-3 which was acceptable but now no body is going to wait for this much time. I think something is wrong on server side. ok thanks again I will update this thread when I get anything to this.
testing LiveHttp on http://www.royalloops.com/pg/videos/play/harry/5711/hrithik-roshan-is-highly-inspired-by-aamir-khan
http://www.royalloops.com/pg/izap_videos_files/image/5698/riz-khan-corruption-in-india.jpg
takes long time complete
and YSlow report ;-(
What's new in Page Speed 1.10?
See the Page Speed documentation for detailed information on the rules used to evaluate web pages.
Page Speed Copyright © 2010 Google Inc.
text
Rulesets
Finding components in the page:
Getting component information:
FUse a Content Delivery Network (CDN)
AAvoid empty src or href
FAdd Expires headers
CCompress components with gzip
APut CSS at top
BPut JavaScript at bottom
AAvoid CSS expressions
n/aMake JavaScript and CSS external
CReduce DNS lookups
BMinify JavaScript and CSS
AAvoid URL redirects
ARemove duplicate JavaScript and CSS
AConfigure entity tags (ETags)
AMake AJAX cacheable
AUse GET for AJAX requests
AReduce the number of DOM elements
AAvoid HTTP 404 (Not Found) error
AReduce cookie size
AUse cookie-free domains
AAvoid AlphaImageLoader filter
ADo not scale images in HTML
AMake favicon small and cacheable
Grade E on Make fewer HTTP requests
This page has 14 external Javascript scripts. Try combining them into one.
Decreasing the number of components on a page reduces the number of HTTP requests required to render the page, resulting in faster page loads. Some ways to reduce the number of components include: combine files, combine multiple scripts into one script, combine multiple CSS files into one style sheet, and use CSS Sprites and image maps.
»Read More
Grade F on Use a Content Delivery Network (CDN)
There are 38 static components that are not on CDN.
You can specify CDN hostnames in your preferences. See YSlow FAQ for details.
User proximity to web servers impacts response times. Deploying content across multiple geographically dispersed servers helps users perceive that pages are loading faster.
»Read More
Grade A on Avoid empty src or href
You may expect a browser to do nothing when it encounters an empty image src. However, it is not the case in most browsers. IE makes a request to the directory in which the page is located; Safari, Chrome, Firefox 3 and earlier make a request to the actual page itself. This behavior could possibly corrupt user data, waste server computing cycles generating a page that will never be viewed, and in the worst case, cripple your servers by sending a large amount of unexpected traffic.
»Read More
Grade F on Add Expires headers
There are 13 static components without a far-future expiration date.
Web pages are becoming increasingly complex with more scripts, style sheets, images, and Flash on them. A first-time visit to a page may require several HTTP requests to load all the components. By using Expires headers these components become cacheable, which avoids unnecessary HTTP requests on subsequent page views. Expires headers are most often associated with images, but they can and should be used on all page components including scripts, style sheets, and Flash.
»Read More
Grade C on Compress components with gzip
There are 2 plain text components that should be sent compressed
Compression reduces response times by reducing the size of the HTTP response. Gzip is the most popular and effective compression method currently available and generally reduces the response size by about 70%. Approximately 90% of today's Internet traffic travels through browsers that claim to support gzip.
»Read More
Grade A on Put CSS at top
Moving style sheets to the document HEAD element helps pages appear to load quicker since this allows pages to render progressively.
»Read More
Grade B on Put JavaScript at bottom
There are 4 JavaScript scripts found in the head of the document
JavaScript scripts block parallel downloads; that is, when a script is downloading, the browser will not start any other downloads. To help the page load faster, move scripts to the bottom of the page if they are deferrable.
»Read More
Grade A on Avoid CSS expressions
CSS expressions (supported in IE beginning with Version 5) are a powerful, and dangerous, way to dynamically set CSS properties. These expressions are evaluated frequently: when the page is rendered and resized, when the page is scrolled, and even when the user moves the mouse over the page. These frequent evaluations degrade the user experience.
»Read More
Grade n/a on Make JavaScript and CSS external
Only consider this if your property is a common user home page.
Using external JavaScript and CSS files generally produces faster pages because the files are cached by the browser. JavaScript and CSS that are inlined in HTML documents get downloaded each time the HTML document is requested. This reduces the number of HTTP requests but increases the HTML document size. On the other hand, if the JavaScript and CSS are in external files cached by the browser, the HTML document size is reduced without increasing the number of HTTP requests.
»Read More
Grade C on Reduce DNS lookups
The components are split over more than 4 domains
The Domain Name System (DNS) maps hostnames to IP addresses, just like phonebooks map people's names to their phone numbers. When you type URL www.yahoo.com into the browser, the browser contacts a DNS resolver that returns the server's IP address. DNS has a cost; typically it takes 20 to 120 milliseconds for it to look up the IP address for a hostname. The browser cannot download anything from the host until the lookup completes.
»Read More
Grade B on Minify JavaScript and CSS
There are 2 components that can be minified
Minification removes unnecessary characters from a file to reduce its size, thereby improving load times. When a file is minified, comments and unneeded white space characters (space, newline, and tab) are removed. This improves response time since the size of the download files is reduced.
»Read More
Grade A on Avoid URL redirects
URL redirects are made using HTTP status codes 301 and 302. They tell the browser to go to another location. Inserting a redirect between the user and the final HTML document delays everything on the page since nothing on the page can be rendered and no components can be downloaded until the HTML document arrives.
»Read More
Grade A on Remove duplicate JavaScript and CSS
Duplicate JavaScript and CSS files hurt performance by creating unnecessary HTTP requests (IE only) and wasted JavaScript execution (IE and Firefox). In IE, if an external script is included twice and is not cacheable, it generates two HTTP requests during page loading. Even if the script is cacheable, extra HTTP requests occur when the user reloads the page. In both IE and Firefox, duplicate JavaScript scripts cause wasted time evaluating the same scripts more than once. This redundant script execution happens regardless of whether the script is cacheable.
»Read More
Grade A on Configure entity tags (ETags)
Entity tags (ETags) are a mechanism web servers and the browser use to determine whether a component in the browser's cache matches one on the origin server. Since ETags are typically constructed using attributes that make them unique to a specific server hosting a site, the tags will not match when a browser gets the original component from one server and later tries to validate that component on a different server.
»Read More
Grade A on Make AJAX cacheable
One of AJAX's benefits is it provides instantaneous feedback to the user because it requests information asynchronously from the backend web server. However, using AJAX does not guarantee the user will not wait for the asynchronous JavaScript and XML responses to return. Optimizing AJAX responses is important to improve performance, and making the responses cacheable is the best way to optimize them.
»Read More
Grade A on Use GET for AJAX requests
When using the XMLHttpRequest object, the browser implements POST in two steps: (1) send the headers, and (2) send the data. It is better to use GET instead of POST since GET sends the headers and the data together (unless there are many cookies). IE's maximum URL length is 2 KB, so if you are sending more than this amount of data you may not be able to use GET.
»Read More
Grade A on Reduce the number of DOM elements
A complex page means more bytes to download, and it also means slower DOM access in JavaScript. Reduce the number of DOM elements on the page to improve performance.
»Read More
Grade A on Avoid HTTP 404 (Not Found) error
There are 2 requests that are 404 Not Found
Making an HTTP request and receiving a 404 (Not Found) error is expensive and degrades the user experience. Some sites have helpful 404 messages (for example, "Did you mean ...?"), which may assist the user, but server resources are still wasted.
»Read More
Grade A on Reduce cookie size
HTTP cookies are used for authentication, personalization, and other purposes. Cookie information is exchanged in the HTTP headers between web servers and the browser, so keeping the cookie size small minimizes the impact on response time.
»Read More
Grade A on Use cookie-free domains
When the browser requests a static image and sends cookies with the request, the server ignores the cookies. These cookies are unnecessary network traffic. To workaround this problem, make sure that static components are requested with cookie-free requests by creating a subdomain and hosting them there.
»Read More
Grade A on Avoid AlphaImageLoader filter
The IE-proprietary AlphaImageLoader filter attempts to fix a problem with semi-transparent true color PNG files in IE versions less than Version 7. However, this filter blocks rendering and freezes the browser while the image is being downloaded. Additionally, it increases memory consumption. The problem is further multiplied because it is applied per element, not per image.
»Read More
Grade A on Do not scale images in HTML
Web page designers sometimes set image dimensions by using the width and height attributes of the HTML image element. Avoid doing this since it can result in images being larger than needed. For example, if your page requires image myimg.jpg which has dimensions 240x720 but displays it with dimensions 120x360 using the width and height attributes, then the browser will download an image that is larger than necessary.
»Read More
Grade A on Make favicon small and cacheable
A favicon is an icon associated with a web page; this icon resides in the favicon.ico file in the server's root. Since the browser requests this file, it needs to be present; if it is missing, the browser returns a 404 error (see "Avoid HTTP 404 (Not Found) error" above). Since favicon.ico resides in the server's root, each time the browser requests this file, the cookies for the server's root are sent. Making the favicon small and reducing the cookie size for the server's root cookies improves performance for retrieving the favicon. Making favicon.ico cacheable avoids frequent requests for it.
»Read More
yr site is s-l-o-wwwww !
- Previous
- 1
- 2
- Next
You must log in to post replies.