LJ Live Test
Well, low and behold !! This morning, the browser cannot access Livejournal.com
Remember I said I was noticing a general slowdown of web content rendering in the browser, probably brought about
by excess code activity conflicting with 3rd party SEO and algorithms? Or my Opera browser update, which is fast as fuck!
***
This site can’t be reached
The webpage at https://pigshitpoet.livejournal.com/ might be temporarily down or it may have moved permanently
to a new web address.
ERR_TUNNEL_CONNECTION_FAILED
**Just I Have Suspected…
**I ran a web speed test and got this. It confirms my suspicions. Shit is so complicated and convoluted on Google,
Livejournal, SEO, Browser, VPN, OS, Popup Ads, etc. that it’s impossible to find your ass from a hole in the ground. Period.
But don’t take my word for it. Here is the proof. Type livejounal.com into the test page:
https://www.webpagetest.org
**Here’s what I got:
https://www.webpagetest.org/result/240612_BiDcBV_9BY/2/experiments/#Resilient
URL:
https://livejournal.com
From: Virginia USA - EC2 - Chrome - Emulated Motorola G (gen 4) - 4G
First View only
Test runs: 3
Connectivity: 9000/9000 Kbps, 170ms Latency
**Performance Summary Website LJ : .[Spoiler (click to open)].livejournal.com Live Test
Is it Quick?
Needs Improvement. This site was very slow to connect and deliver initial code. It began rendering content with considerable delay. There were 6 render-blocking requests. The largest content rendered later than ideal.
Is it Usable?
Needs Improvement. This site had major layout shifts. It took a long time to become interactive. It had 8 accessibility issues, 3 critical. Some HTML was generated after delivery, potentially delaying usability.
Is it Resilient?
Needs Improvement. This site had many render-blocking 3rd party requests that could be a single point of failure. It had 12 security issues, 1 high-priority. Some HTML was generated after delivery, which can cause fragility.
*Here’s a Positive Aspect…
Layout shifts are not caused by images lacking aspect ratio
This is great. Images with width and height attributes allow the browser to better predict the space an image will occupy in a layout before it loads, reducing layout shifts and improving your CLS metric score.
*Also Between Yandex and Google you have a Shitshow!
**Is it Usable?
The main thread was blocked for 6692 ms
When files block the main thread, users are unable to interact with the page content. Typically, parsing and executing large JavaScript files, as well as running long JavaScript tasks can block the main thread and should be avoided. These files had high thread blocking times:
270 ms: https://www.livejournal.com/
1443 ms: https://ssp.rambler.ru/capirs_async.js
4406 ms: https://l-stat.livejournal.net/js/??.ljlib.js?v=1718107956
742 ms: https://l-stat.livejournal.net/js/??mainpage/ljtoday.js,mainpage/main.js,mainpage/app.js,scheme/schemius/index.js,widgets/angular/login.js,scheme/medius.js?v=1718107956
281 ms: https://fundingchoicesmessages.google.com/f/AGSKWxW4FWZuUtdQFTVPtyUM4nsYfj3wG8QdpDhzmDLVqXGEglR_b97iM8a5aTdO549-sZ58LY6aha4qN4XrLBOqmT8=
234 ms: https://www.googletagmanager.com/gtm.js?id=GTM-KJBSQR
429 ms: https://www.googletagmanager.com/gtag/js?id=G-1V2YHKGDNK
239 ms: https://vp.rambler.ru/player/sdk.js
276 ms: https://top-fwz1.mail.ru/js/code.js
382 ms: https://st.top100.ru/top100/top100.js
208 ms: https://privacy-cs.mail.ru/static/sync-loader.js 483 ms: https://mc.yandex.ru/metrika/tag.js
171 ms: https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?fcd=true
582 ms: https://yandex.ru/ads/system/context.js
200 ms: https://yastatic.net/partner-code-bundles/1042322/7a9856038fa7e54b2592.js
OK. So, here’s a quirk out of hell, I use Mac OS, I just discovered when doing a system optimization, that although the Safari browser icon seems it is off, the cleanup says it is still in use and needs to Force Quit Safari to run the cleanup Scan. What is Safari doing in the background when it is not active? So, add Apple Safari into the mix. Fucking cookies.
Or, for all I know it could be the Antivirus running in the background. Who knows?
Accessibility Issues were Detected
Axe found 8 accessibility issues: 3 critical, 4 serious, 1 minor
**Is it Resilient?
Potential SPOF: 6 3rd-party requests are blocking page rendering.
**By default, references to external JavaScript and CSS files will block the page from rendering. Third-party blocking requests are particularly risky, as your page's access relies on their response time and availability.'
https://fonts.googleapis.com/css2?family=El+Messiri:wght@700&display=swap
https://l-stat.livejournal.net/??schemius_v4/header_v5.css,schemius_v4/menu-aside.css,schemius_v4/header_v5-adaptive.css,schemius_v4/header-journal.css,schemius_v4/header-journal-adaptive.css,lj-basestrap.css,lj-basestrap-app.css,flatbutton.css,svg/flaticon.css,svg/headerextra.css,medius/scheme/components.css,core/components/basepopup.css,core/components/lightcontrols.css,core/components/note-inner.css,core/components/alert.css,popup/popup-suggestion.css,popup/popup-trump.css,popup/popup-map-invite.css,popup/push-woosh-popup.css,notifications/list.css,schemius_v4/asap-news.css,components/interest.css,components/cookies-banner.css,components/modal-repost.css,components/buttons.css,components/promo-video.css,schemius_v4/normalize.css,schemius_v4/layout.css,schemius_v4/print.css?v=1718107956
https://l-stat.livejournal.net/??widgets/likes.css,main_v3.css,promo_wrappers.css,entryunit_v4.css,ljuser/ljuser.css,widgets/flatwidget.css,promo/promocontrols.css,widgets/getstartedwithlj.css,widgets/rutos.css,widgets/login_v2.css,msgsystem.css?v=1718107956
https://l-stat.livejournal.net/??proximanova-opentype.css?v=1718107956
https://l-stat.livejournal.net/js/??.ljlib.js?v=1718107956
https://l-stat.livejournal.net/js/??mainpage/ljtoday.js,mainpage/main.js,mainpage/app.js,scheme/schemius/index.js,widgets/angular/login.js,scheme/medius.js?v=1718107956
Preconnect 3rd Party Hosts
This experiment will add a link with rel="preconnect" for specified hosts, which saves time for those steps when the resource is later requested.
By default, references to external JavaScript and CSS files will block the page from rendering. Third-party blocking requests are particularly risky, as your page's access relies on their response time and availability.'
Several security vulnerabiities were detected by Snyk Snyk has found
12 security vulnerabilities: 1 high, 9 medium, 2 low.
Final HTML (DOM) size is significantly larger than initially delivered HTML (257.42kb larger, or 30.05% of total HTML).
Typically this is due to over-reliance on JavaScript for generating content, but increases can also happen as a result of browsers normalizing HTML structure as well. Common issues such as JavaScript errors and third-party network delays and outages can present potential single points of failure.
**LJ performance really sucks.
*Some of it has to do with Fonts…
**One of the first things I learned in PC Land, is that the biggest cause of glitches in rendering of graphic software as well as Word doc is FONTS>
1 font is hosted on 3rd-party hosts
Fonts on 3rd party domains may take longer to load due to DNS and connection steps that are not necessary when fonts are hosted on the same domain.
https://yastatic.net/s3/home/fonts/ys/3/text-variable-full.woff2
Zero custom fonts load in ways that delay text visibility.
When fonts are loaded with default display settings, like font-display="block", browsers will hide text entirely for several seconds instead of showing text with a fallback font. font-display: swap will fix this.
94 files were hosted without using a CDN.
40 static files have inadequate cache settings.
61 requests are resulting in an HTTP redirect.
Final HTML (DOM) size is significantly larger than initially delivered HTML (257.42kb larger, or 30.05% of total HTML).
This is possibly, Livejournal, Opera Browser, VPN, Russian Fonts, 3rd Party Ads, who knows?
**I’m not a code warrior, but I know WYSIWYG, and this is not it. Now becomes WASS (What A ShitShow) or SFB (Shit For Brains) - Use FTF Workaround (ie. Fix-The-Fux)
Do you think LJ ever run a test on themselves? Are these just overladen dinosaur operations requiring 32GB just to run a command? Or are they all just amateur wirings?
CleanMyMac has found that you are running out of both you are running out of both physical and virtual memory. Let’s fix it.
So I also ran a deep scan for Malware. And nothing was found. And I restarted my System and it seemed to help.
*Your request has been filed. You can track the progress of your request at:
https://www.livejournal.com/support/request/?id=2198055&auth=q74pbr3j8kad73q
If you have any other questions or comments, you can add them to that request at any time.
.LJ Live Test
This was Wednesday morning. This is what I woke up to. Just to post this…
Wait. OK, now I get this popup of failed page, then it goes to my page. WTF?
Fuck me, eh?
dr. π (pi)
.
Remember I said I was noticing a general slowdown of web content rendering in the browser, probably brought about
by excess code activity conflicting with 3rd party SEO and algorithms? Or my Opera browser update, which is fast as fuck!
***
This site can’t be reached
The webpage at https://pigshitpoet.livejournal.com/ might be temporarily down or it may have moved permanently
to a new web address.
ERR_TUNNEL_CONNECTION_FAILED
**Just I Have Suspected…
**I ran a web speed test and got this. It confirms my suspicions. Shit is so complicated and convoluted on Google,
Livejournal, SEO, Browser, VPN, OS, Popup Ads, etc. that it’s impossible to find your ass from a hole in the ground. Period.
But don’t take my word for it. Here is the proof. Type livejounal.com into the test page:
https://www.webpagetest.org
**Here’s what I got:
https://www.webpagetest.org/result/240612_BiDcBV_9BY/2/experiments/#Resilient
URL:
https://livejournal.com
From: Virginia USA - EC2 - Chrome - Emulated Motorola G (gen 4) - 4G
First View only
Test runs: 3
Connectivity: 9000/9000 Kbps, 170ms Latency
**Performance Summary Website LJ : .[Spoiler (click to open)].livejournal.com Live Test
Is it Quick?
Needs Improvement. This site was very slow to connect and deliver initial code. It began rendering content with considerable delay. There were 6 render-blocking requests. The largest content rendered later than ideal.
Is it Usable?
Needs Improvement. This site had major layout shifts. It took a long time to become interactive. It had 8 accessibility issues, 3 critical. Some HTML was generated after delivery, potentially delaying usability.
Is it Resilient?
Needs Improvement. This site had many render-blocking 3rd party requests that could be a single point of failure. It had 12 security issues, 1 high-priority. Some HTML was generated after delivery, which can cause fragility.
*Here’s a Positive Aspect…
Layout shifts are not caused by images lacking aspect ratio
This is great. Images with width and height attributes allow the browser to better predict the space an image will occupy in a layout before it loads, reducing layout shifts and improving your CLS metric score.
*Also Between Yandex and Google you have a Shitshow!
**Is it Usable?
The main thread was blocked for 6692 ms
When files block the main thread, users are unable to interact with the page content. Typically, parsing and executing large JavaScript files, as well as running long JavaScript tasks can block the main thread and should be avoided. These files had high thread blocking times:
270 ms: https://www.livejournal.com/
1443 ms: https://ssp.rambler.ru/capirs_async.js
4406 ms: https://l-stat.livejournal.net/js/??.ljlib.js?v=1718107956
742 ms: https://l-stat.livejournal.net/js/??mainpage/ljtoday.js,mainpage/main.js,mainpage/app.js,scheme/schemius/index.js,widgets/angular/login.js,scheme/medius.js?v=1718107956
281 ms: https://fundingchoicesmessages.google.com/f/AGSKWxW4FWZuUtdQFTVPtyUM4nsYfj3wG8QdpDhzmDLVqXGEglR_b97iM8a5aTdO549-sZ58LY6aha4qN4XrLBOqmT8=
234 ms: https://www.googletagmanager.com/gtm.js?id=GTM-KJBSQR
429 ms: https://www.googletagmanager.com/gtag/js?id=G-1V2YHKGDNK
239 ms: https://vp.rambler.ru/player/sdk.js
276 ms: https://top-fwz1.mail.ru/js/code.js
382 ms: https://st.top100.ru/top100/top100.js
208 ms: https://privacy-cs.mail.ru/static/sync-loader.js 483 ms: https://mc.yandex.ru/metrika/tag.js
171 ms: https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?fcd=true
582 ms: https://yandex.ru/ads/system/context.js
200 ms: https://yastatic.net/partner-code-bundles/1042322/7a9856038fa7e54b2592.js
OK. So, here’s a quirk out of hell, I use Mac OS, I just discovered when doing a system optimization, that although the Safari browser icon seems it is off, the cleanup says it is still in use and needs to Force Quit Safari to run the cleanup Scan. What is Safari doing in the background when it is not active? So, add Apple Safari into the mix. Fucking cookies.
Or, for all I know it could be the Antivirus running in the background. Who knows?
Accessibility Issues were Detected
Axe found 8 accessibility issues: 3 critical, 4 serious, 1 minor
**Is it Resilient?
Potential SPOF: 6 3rd-party requests are blocking page rendering.
**By default, references to external JavaScript and CSS files will block the page from rendering. Third-party blocking requests are particularly risky, as your page's access relies on their response time and availability.'
https://fonts.googleapis.com/css2?family=El+Messiri:wght@700&display=swap
https://l-stat.livejournal.net/??schemius_v4/header_v5.css,schemius_v4/menu-aside.css,schemius_v4/header_v5-adaptive.css,schemius_v4/header-journal.css,schemius_v4/header-journal-adaptive.css,lj-basestrap.css,lj-basestrap-app.css,flatbutton.css,svg/flaticon.css,svg/headerextra.css,medius/scheme/components.css,core/components/basepopup.css,core/components/lightcontrols.css,core/components/note-inner.css,core/components/alert.css,popup/popup-suggestion.css,popup/popup-trump.css,popup/popup-map-invite.css,popup/push-woosh-popup.css,notifications/list.css,schemius_v4/asap-news.css,components/interest.css,components/cookies-banner.css,components/modal-repost.css,components/buttons.css,components/promo-video.css,schemius_v4/normalize.css,schemius_v4/layout.css,schemius_v4/print.css?v=1718107956
https://l-stat.livejournal.net/??widgets/likes.css,main_v3.css,promo_wrappers.css,entryunit_v4.css,ljuser/ljuser.css,widgets/flatwidget.css,promo/promocontrols.css,widgets/getstartedwithlj.css,widgets/rutos.css,widgets/login_v2.css,msgsystem.css?v=1718107956
https://l-stat.livejournal.net/??proximanova-opentype.css?v=1718107956
https://l-stat.livejournal.net/js/??.ljlib.js?v=1718107956
https://l-stat.livejournal.net/js/??mainpage/ljtoday.js,mainpage/main.js,mainpage/app.js,scheme/schemius/index.js,widgets/angular/login.js,scheme/medius.js?v=1718107956
Preconnect 3rd Party Hosts
This experiment will add a link with rel="preconnect" for specified hosts, which saves time for those steps when the resource is later requested.
By default, references to external JavaScript and CSS files will block the page from rendering. Third-party blocking requests are particularly risky, as your page's access relies on their response time and availability.'
Several security vulnerabiities were detected by Snyk Snyk has found
12 security vulnerabilities: 1 high, 9 medium, 2 low.
Final HTML (DOM) size is significantly larger than initially delivered HTML (257.42kb larger, or 30.05% of total HTML).
Typically this is due to over-reliance on JavaScript for generating content, but increases can also happen as a result of browsers normalizing HTML structure as well. Common issues such as JavaScript errors and third-party network delays and outages can present potential single points of failure.
**LJ performance really sucks.
*Some of it has to do with Fonts…
**One of the first things I learned in PC Land, is that the biggest cause of glitches in rendering of graphic software as well as Word doc is FONTS>
1 font is hosted on 3rd-party hosts
Fonts on 3rd party domains may take longer to load due to DNS and connection steps that are not necessary when fonts are hosted on the same domain.
https://yastatic.net/s3/home/fonts/ys/3/text-variable-full.woff2
Zero custom fonts load in ways that delay text visibility.
When fonts are loaded with default display settings, like font-display="block", browsers will hide text entirely for several seconds instead of showing text with a fallback font. font-display: swap will fix this.
94 files were hosted without using a CDN.
40 static files have inadequate cache settings.
61 requests are resulting in an HTTP redirect.
Final HTML (DOM) size is significantly larger than initially delivered HTML (257.42kb larger, or 30.05% of total HTML).
This is possibly, Livejournal, Opera Browser, VPN, Russian Fonts, 3rd Party Ads, who knows?
**I’m not a code warrior, but I know WYSIWYG, and this is not it. Now becomes WASS (What A ShitShow) or SFB (Shit For Brains) - Use FTF Workaround (ie. Fix-The-Fux)
Do you think LJ ever run a test on themselves? Are these just overladen dinosaur operations requiring 32GB just to run a command? Or are they all just amateur wirings?
CleanMyMac has found that you are running out of both you are running out of both physical and virtual memory. Let’s fix it.
So I also ran a deep scan for Malware. And nothing was found. And I restarted my System and it seemed to help.
*Your request has been filed. You can track the progress of your request at:
https://www.livejournal.com/support/request/?id=2198055&auth=q74pbr3j8kad73q
If you have any other questions or comments, you can add them to that request at any time.
.LJ Live Test
This was Wednesday morning. This is what I woke up to. Just to post this…
Wait. OK, now I get this popup of failed page, then it goes to my page. WTF?
Fuck me, eh?
dr. π (pi)
.