The problem that i have is like this:
I did a YSlow test and under the Statistics Pie Chart View i have a wrong pie chart diagram. The Empty cache displays 11 requests and the primed cache displays 2 requests.
Now one of the two request is a request for a HTML file which the Net Panel shows as 304 Not Modified - but YSlow till shows it in the pie chart as a new request with file size.
Now as far as i know is that if a 304 Not Modified request is made, it shows it under the primed cache listing but with 0.0 KB file size and not in the pie chart.
Is this some bug? Somebody have had some experience?
---- PS: It worked fine 2 hours ago and YES I'm quite sure i did not change any settings ---
Sometimes there can be differences between the Net panel and YSlow components report. See this page on the YSlow FAQ that explains some of the reasons why this can happen.
If you add here the URL of the page you're analyzing, a better answer may be possible.
Related
page speed score - ?
I insert the website and after the score appears just with a "?"
Your site is slow to reach. See screenshot attached.
Running your site from California, it takes over 3.2 seconds for FCP - first contentful paint.
This is not good. This is why page speed is unable to take screen shots as it is taking too long. Hence it times out and displays "?" if any of its tests are failing due to timeout.
You want to speed up FCP. Load only important elements on your viewport. Lazy load images and use defer, async for scripts.
You can gain better insights with Lighthouse. Use Chrome browser, incognito mode, load up your site and use incognito mode. It tells you things you need to fix.
Good luck
Checked under the Speed Index section, there is an error which looks like below.
Speed Index
Error!
Chrome didn't collect any screenshots during the page load. Please make sure there is content visible on the page, and then try re-running Lighthouse. (SPEEDINDEX_OF_ZERO)
Fix that and try again it should show the number.
Hope this helps.
So I downloaded a MathJax package, unpacked it, modified the settings and uploaded the files to an http domain. Everything worked as well as possible for more than a year.
Two days ago, I copied all files (including the database) to a new domain, activated SSL and modified .htaccess to translate all addresses into https. This works perfectly for everything except MathJax "Can't load web font" resulting in a 10 second delay every time it attempts to draw expressions.
Neither Firefox nor Chrome show any kind of errors in the console or failed file reads (cache off, 200 OK). The only effect in the browsers is that there is a 9-10 second gap between /mathjax/jax/output/HTML-CSS/fonts/STIX-Web/Main/Regular/Main.js and /mathjax/jax/output/HTML-CSS/fonts/STIX-Web/Main/Italic/Main.js.
Approximate timeline …
2 s: read (success) /mathjax/jax/output/HTML-CSS/fonts/STIX-Web/Main/Regular/Main.js
11.5 s: read (success) /mathjax/jax/output/HTML-CSS/fonts/STIX-Web/Main/Italic/Main.js
12 s: read (success) /mathjax/fonts/HTML-CSS/STIX-Web/woff/STIXMathJax_Main-Regular.woff
Log (last 4 lines) …
Loading [MathJax]/jax/output/HTML-CSS/fonts/STIX-Web/Main/Regular/Main.js
Loading web-font STIX-Web/Main/Regular
Can't load web font STIX-Web/Main/Regular
Loading [MathJax]/jax/output/HTML-CSS/fonts/STIX-Web/Main/Italic/Main.js
In the timeline, the seconds are the timestamps of the attempts, not the durations. Those are 0-100 ms each.
What I have tried:
Reset .htaccess, loaded everything with http, recopied all MathJax files from old domain to the new one and made sure all directories and files have the proper permissions. I have also entered the paths (in the address bar) to the failing woff files and they download properly. Furthermore, I have disabled SSL and modified the script tags to read the settings file and MathJax from the old domain – still a 10 second delay before attempting to read font files.
How can I tell why MathJax can't load a web font? Why does MathJax, with identical code, add a delay on one site but not the other? Is there a way to troubleshoot this?
Update:
This is now really weird!! After cross-loading files between the sites, I have narrowed down the error to be connected to my CSS file!… which passes validation perfectly (and contains no font changes, between sites, at all). The main change I've done in that file is to add wrapping divs to most elements directly inside body in order to style the wrappers at 100% width, but have the content at 80%.
It turns out that MathJax (2.6.0 and 2.7.2) failed to load a font because I set a min-width on #MathJax_Font_Test. I did not do this on purpose and had no idea it would break. Here's my fix:
body > div > div:not(#MathJax_Font_Test) {
min-width: 960px;
}
The Glimpse javascript panel shows a nice summary of http timing information. The time spent on the wire, the time on the server, etc....
However when you view the information using the pop out, that information is no longer accessible. I can't find http timings anywhere. Is there anyway to view this information without viewing it directly through the javascript injected panel?
Unfortunately, at this point, the answer is no.
There has been some community work to bring the full data set available from the navigation timing API into Glimpse.
That effort is a bit stale now, but if you'd like to pick it back up you'd be able to get not only http timings, but all of the following:
navigationStart
unloadEventStart
unloadEventEnd
redirectStart
redirectEnd
fetchStart
domainLookupStart
domainLookupEnd
connectStart
connectEnd
secureConnectionStart
requestStart
responseStart
responseEnd
domLoading
domInteractive
domContentLoadedEventStart
domContentLoadedEventEnd
domComplete
loadEventStart
loadEventEnd
AND it would work in almost all browsers (excluding oldIE).
I have been working on this site for some time and just launched it for a client.
People have actually had trouble beleiving I had done it on WordPress, though I don't see why...
Anyway, I suddenly see that the form fields of one of the forms on the site (Newsletter Registration) disappear while on IE, you get to see them for a second and puff, they're gone. I did check this previously on IE and it worked, I especially used CSS3 PIE to get the rounded effect for the fields on IE...
Link to website: http://www.doritsivan.com (hope this isn't considered promotion, not my intention)
site is based on WordPress and jQuery.
resolved the issue, thank you all. it was a bad case of relative vs. absolute positioning and the fields decided to go away (literaly)
A bunch of debugging with firebug-lite (btw was real to get it to work on my IE, kept on crashing or refusing to load altogether combined with IE popup and security issues) and I understoid that this was the issue, then some pixel fiddling and all was good. rechecked in Chrome, saw that result was exactly the same. job done
I'm using XSL-FO (Formatting Objects) in XMLSpy with Apache FOP.
When I flow content from a first page having a simple-page-master with a wide region-body onto a second (rest) page having a narrow region-body, the content on the second page has the same width as the content on the first page, overflowing the body. This also happens if I set the column-count on the second page to be greater than the column-count on the first page.
How do I force the engine to recognize that the available horizontal space has been decreased, and adjust the body (or column) width accordingly?
An example of the problem can be seen here (use with any XML document that contains sufficient text content to flow from page 1 to page 2):
http://pastebin.com/VGyWYNBS
filling in with randome text, your xsl-fo works well with a commercial formatter,
one column first page, three on the second and third pages?
I submitted this to Apache using Bugzilla:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50794
Chris Bowditch posted this response there:
the problem you describe is known as
Changing IPD problem. That is a known
issue in 0.95. For v1.0 we developed a
fix for it that works in most cases.
There are some limitations related to
lists and tables, but for regular
text, upgrading to FOP v1.0 should
resolve your problems.