Google Core Web Vitals में Interaction To Next Paint (INP) क्या है? | Interaction To Next Paint kya hai

Google ne Google Search Console mein Core Web Vitals report mein Interaction to Next Paint (INP) ko shaamil karne ka announcement kiya hai, jisse aap apne scores dekh sakte hain. Ye badlav March 2024 se shuru hokar First Input Delay (FID) ko Core Web Vitals metric ke roop mein badal dega. Google ne is badlav ki ghoshna Google I/O mein ki thi aur is par ek saal se hint diya ja raha tha. Lekin ab ye official hai. Is article mein INP kaise kaam karta hai, isko kaise measure kiya ja sakta hai aur isko sudhaarne ke liye resources ke baare mein jaankari di gayi hai.

Interaction to Next Paint Kya Hai

INP (Interaction to Next Paint) ek metric hai jo ek page ki overall responsivenes ko user interactions ke madhyam se evaluate karta hai. Ye metric ek user ke page par kiye gaye click, tap aur keyboard interactions ki latency ko observe karke calculate hota hai. INP ki final value wo interaction hoti hai jo sabse zyada samay leti hai, outliers ko ignore karke.

INP ka calculation kaise hota hai

Jaisa ki upar bataya gaya hai, INP ka calculation page par kiye gaye sabhi interactions ko observe karke kiya jata hai. Aam taur par, maximum latency wala interaction INP ke roop mein report kiya jata hai. Lekin, agar kisi page par bahut saare interactions hote hain, toh kabhi-kabhi kuch aniyamit hiccups ki wajah se ek aam taur par responsive site par bhi atyadhik latency wala interaction ho sakta hai. Jitne zyada interactions hote hain, utni zyada probability hoti hai ki aisa ho. Isko samjhane ke liye aur aise pages ki asli responsivenes ka behtar measure dene ke liye, har 50 interactions ke liye sabse zyada latency wala interaction ko ignore kiya jata hai. Jyadatar page experiences mein 50 se kam interactions hote hain, isliye wo sabse zyada latency wala interaction report kiya jata hai. Uske baad 75th percentile of all the page views ko report kiya jata hai, jisse outliers ko aur bhi remove karke ek value milti hai jo jyadatar users experience karte hain ya usse behtar hoti hai.

Ek interaction ek group of event handlers hota hai jo ek logical user gesture ke dauran trigger hote hain. For example, “tap” interactions on a touchscreen device mein multiple events, jaise pointerup, pointerdown, aur click, shaamil hote hain. Ek interaction JavaScript, CSS, built-in browser controls (jaise form elements), ya in sab ka combination ke dwara drive kiya ja sakta hai.

Ek interaction ki latency us group ke sabse zyada samay ke duration se hoti hai, jisse user interaction shuru karta hai aur agle frame mein visual feedback ke saath dikhaya jata hai.

एक अच्छा INP स्कोर क्या है? (What is a good INP score?)

Ek responsiveness metric par “accha” ya “bura” label lagana mushkil hai. Ek taraf, aapko aise development practices ko encourage karna hai jo acchi responsivenes ko priority dete hain. Dusri taraf, aapko ye bhi dhyan mein rakhna hoga ki log kis tarah ke devices ka upyog karte hain, jisse realistic development expectations banaye ja sake.

Acchi responsivenes ke saath user experiences provide karne ke liye, ek accha threshold jo measure kiya ja sakta hai, wo field mein recorded page loads ke 75th percentile hai, mobile aur desktop devices ke alag-alag segments mein:

• Agar INP 200 milliseconds se kam hai ya 200 milliseconds ke barabar hai, toh aapke page ki responsivenes acchi hai.
• Agar INP 200 milliseconds se zyada hai aur 500 milliseconds se kam hai ya 500 milliseconds ke barabar hai, toh aapke page ki responsivenes sudhaar ki zaroorat hai.
• Agar INP 500 milliseconds se zyada hai, toh aapke page ki responsivenes buri hai.

Aksar interactivity ka mukhya karan JavaScript hota hai, lekin browser JavaScript se sambandhit na ho, jaise checkboxes, radio buttons, aur CSS se sambandhit controls ke dwara bhi interactivity provide karte hain.

INP ke hisaab se, sirf nimnlikhit interaction types observe kiye jaate hain:

• Mouse se click karna.
• Touchscreen wale device par tap karna.
• Physical ya onscreen keyboard se ek key dabana.

Mahatvapurna: INP mein hover aur scrolling ka hissa nahi hai. Lekin, keyboard se scrolling karna (space bar, page up, page down, aadi) ek keystroke ke dwara hota hai, jisse INP dwara measure kiye jaane waale aur bhi events trigger ho sakte hain. Is tarah ki resulting scrolling ko INP ke calculation mein shaamil nahi kiya jata hai.

Interactions ya toh main document mein hoti hain ya fir document mein embedded iframes mein—jaise ki embedded video par play button click karna. Aam users ko ye pata nahi hota ki kya iframe mein hai ya nahi. Isliye, top level page ke user experience ko measure karne ke liye INP iframes ke andar zaroori hai. Dhyan dein ki JavaScript Web APIs iframe contents tak access nahi kar sakte, isliye INP ko iframe ke andar measure nahi kiya jaa sakta hai aur isme CrUX (Chrome User Experience Report) aur RUM (Real User Monitoring) ke beech ek antar dikhega.

Interactions do parts se milkar bante hain, jisme har part mein multiple events hote hain. For example, ek keystroke mein keydown, keypress, aur keyup events shaamil hote hain. Tap interactions pointerup aur pointerdown events ko shaamil karte hain. Interaction ke andar sabse zyada samay ka event interaction ki latency ke roop mein chuna jata hai. INP tab calculate hota hai jab user page ko chhod deta hai, jisse ek single value milti hai jo poori page ke lifecycle mein page ki overall responsivenes ko represent karti hai. Kam INP ka matlab hai ki page user input ke liye consistent tarike se responsive hai.

INP aur First Input Delay (FID) mein kya antar hai?

Jab INP sabhi page interactions ko consider karta hai, tab First Input Delay (FID) sirf pehle interaction ko hi dekhta hai. FID sirf pehle interaction ki input delay ko measure karta hai, event handlers ko chalane mein ya agle frame ko present karne mein hone waali deri ko nahi.

FID bhi ek load responsiveness metric hai, jiska logic ye hai ki agar ek page ke saath loading phase mein kiya gaya pehla interaction mehsus hone waali input delay kam hai ya bilkul nahi hai, toh page ne ek accha pehla impression diya hai.

INP pehle impressions se zyada hai. Jab sabhi interactions ko sample karke dekha jata hai, tab responsivenes ko comprehensive tarike se assess kiya ja sakta hai, jisse INP FID se zyada reliable indicator ban jata hai overall responsivenes ka.

यदि कोई INP Value रिपोर्ट नहीं किया गया तो क्या होगा?

Ho sakta hai ki kisi page ka koi INP value report na ho. Iska kuch karan ho sakte hain:

Page load hua, lekin user ne click, tap ya keyboard se koi key press nahi kiya.
Page load hua, lekin user ne scrolling ya element ke upar hover karna jaise gestures se interaction kiya, jisme click, tap ya keyboard ka istemal nahi hua. INP ka calculation mein in gestures ko shaamil nahi kiya jata hai.
Page ko ek bot access kar raha hai, jaise ki search crawler ya headless browser, jiske pass page ke saath interaction karne ke liye koi script nahi hai.

INP ko kaise measure karein?

INP ko measure karne ke liye field mein aur lab mein alag-alag tools ka istemal kiya jaa sakta hai.

Mahatvapurna : Apne website ka INP measure karne ka sabse accha tarika actual users se field mein metrics collect karna hai. Agar aap performance assess karne ke liye lab data par depend karte hain, toh thoda samay nikalkar “Why lab and field data can be different (and what to do about it)” ko padhne mein samay vyatit karein.

Field mein #

Ideally, aapka INP optimize karne ka safar field data se shuru hoga. Field data Real User Monitoring (RUM) se aapko sirf page ke INP value ke alawa, us value ki wajah se responsible interaction ko highlight karne wale contextual data bhi provide karega. Ye data batayega ki interaction page load ke dauran ya uske baad mein hua, interaction ka type (click, keypress, ya tap), aur dusre mahatvapurna jaankari. Agar aapka website Chrome User Experience Report (CrUX) mein shaamil hone ke layak hai, toh aap CrUX ke through INP ke field data ko jaldi se PageSpeed Insights (aur dusre Core Web Vitals) mein access kar sakte hain. Kam se kam, aap apne website ke origin-level ka INP picture dekh sakte hain, lekin kuch cases mein, aap page-level data bhi prapt kar sakte hain.

Halaanki, CrUX aapko high level par problem batane ke liye upyogi hai, lekin aksar ye sufficient detail provide nahi karta hai jisse problem ko puri tarah samajh sakein. RUM ka upayog aapko detail mein drill down karne mein madad karta hai jaise ki pages, users ya user interactions jo slow interactions ka samna kar rahe hain. INP ko individual interactions se jodne ki capability guesswork aur bekaar ki koshish se bachati hai.

Lab mein

Yadi aapke paas field data hai jo aapko slow interactions ka sanket deta hai, toh lab mein testing shuru karne ki ichha hogi. Lekin agar field data available nahi hai, toh lab mein slow interactions ko reproduce karne ke kuch strategies hain. Ye strategies common user flows ko follow karne aur raaste ke beech mein interactions ko test karne ke include karte hain, sath hi page load ke dauran—jab main thread aksar sabse vyast hota hai—page ke saath interaction karne se, user experience ke us mahatvapurna hisse mein slow interactions ko surface karna.

INP ko kaise sudharein?

INP ko optimize karne ke liye ek guide collection uplabdh hai, jisse aapko field mein slow interactions ko pehchaanne aur lab data ka upayog karke unko alag-alag tarike se optimize karne ke liye madad milegi.

Source: Official Google Developers Link

Interaction To Next Paint (INP) FAQ’s