Now you can have a look of my all screeners at one place
No need to run all screeners separately
Save this link
All screeners complied and visible under one roof
Download Stocks in list in excel too
Keep learning
Keep
More from Vibhor Varshney
Irctc - updated chart and follow up
Another fresh breakout making HH-HL
volume spike seen today
Unlock process started which will help irctc to have upcoming good quarter results
Hits 2100+
Keep holding
2300-2500 short term targets
4992 long term target
Monopoly company https://t.co/mlIErwRuP5
Another fresh breakout making HH-HL
volume spike seen today
Unlock process started which will help irctc to have upcoming good quarter results
Hits 2100+
Keep holding
2300-2500 short term targets
4992 long term target
Monopoly company https://t.co/mlIErwRuP5

Irctc
— Vibhor Varshney (@nakulvibhor) June 7, 2021
Another fresh breakout
Unlock process started in Mumbai - Delhi - up and few other states will help irctc to have upcoming good quarter results
Hits 2100+
Keep holding
2300-2500 short term targets
4992 long term target
Monopoly company
One can add now as well
\U0001f44d\U0001f44d https://t.co/O5M3hj8Mhk
More from Screeners
VWAP for intraday Trading Part -2
A small thread.
PART 1 - https://t.co/ooxepHpYKL
Traders show your support by like & retweet to benefit all
@Mitesh_Engr @ITRADE191 @ProdigalTrader @nakulvibhor @RajarshitaS @Puretechnicals9 @AnandableAnand @Anshi_________ @ca_mehtaravi
Chart 1
Chart 2
Chart 3
Chart 4
A small thread.
PART 1 - https://t.co/ooxepHpYKL
Traders show your support by like & retweet to benefit all
@Mitesh_Engr @ITRADE191 @ProdigalTrader @nakulvibhor @RajarshitaS @Puretechnicals9 @AnandableAnand @Anshi_________ @ca_mehtaravi

VWAP for intraday Trading Part -1
— Learn to Trade (@learntotrade365) August 28, 2021
A small thread PART -2 will be released tomorrow
Traders show your support by like & retweet to benefit all@Mitesh_Engr @ITRADE191 @ProdigalTrader @nakulvibhor @ArjunB9591 @CAPratik_INDIAN @RajarshitaS @Stockstudy8 @vivbajaj @Prakashplutus pic.twitter.com/y8bwisM4hB
Chart 1

Chart 2

Chart 3

Chart 4

You May Also Like
First update to https://t.co/lDdqjtKTZL since the challenge ended – Medium links!! Go add your Medium profile now 👀📝 (thanks @diannamallen for the suggestion 😁)
Just added Telegram links to https://t.co/lDdqjtKTZL too! Now you can provide a nice easy way for people to message you :)
Less than 1 hour since I started adding stuff to https://t.co/lDdqjtKTZL again, and profile pages are now responsive!!! 🥳 Check it out -> https://t.co/fVkEL4fu0L
Accounts page is now also responsive!! 📱✨
💪 I managed to make the whole site responsive in about an hour. On my roadmap I had it down as 4-5 hours!!! 🤘🤠🤘

Just added Telegram links to https://t.co/lDdqjtKTZL too! Now you can provide a nice easy way for people to message you :)

Less than 1 hour since I started adding stuff to https://t.co/lDdqjtKTZL again, and profile pages are now responsive!!! 🥳 Check it out -> https://t.co/fVkEL4fu0L

Accounts page is now also responsive!! 📱✨

💪 I managed to make the whole site responsive in about an hour. On my roadmap I had it down as 4-5 hours!!! 🤘🤠🤘
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.