Masu haɓaka burauzar Chrome suna aiki sosai kuma a cikin kwanakin ƙarshe da sun fito da canje-canje daban-daban kuma daga waɗanda aka sanar ɗayansu shine haɓakar kayan aikin ɗagowa don abubuwan shafin yanar gizo, wanda ke ba da damar ɗaukar abun ciki wanda yake waje da yankin da ake gani har sai mai amfani ya gungura shafin zuwa wurin kai tsaye kafin abu ya faɗi.
A baya a cikin Chrome an riga an aiwatar da wannan yanayin don hotuna, amma yanzu masu kirkirar Chrome sun ci gaba da mataki daya kuma sun kara ikon ragon loda iframes.
Don sarrafa shafuka masu laula a cikin alamar "iframe", an ƙara sifar "ɗora Kwatancen," wanda za'a iya saita shi zuwa "jinkirta" (jinkirta saukar da shi), "himma" (zazzagewa gaba ɗaya) da "atomatik" (don jinkirta loda yadda ake amfani da burauzar, idan kun kunna Yanayin Lite).
Ana sa ran ɗaukar raggo don rage yawan amfani da ƙwaƙwalwar ajiya, rage zirga-zirga da kuma kara saurin bude shafin da farko. Misali, idan aka kunna sabon yanayin, toshe tare da tallan Twitter, Facebook da YouTube da kuma Widget din za su daina yin lodi nan take, idan mai amfani ba ya ganin su, har sai mai amfani ya nade shafin zuwa wani matsayi a gaban wadannan tubalan.
A cewar masu haɓaka, a matsakaiciyar ragowa zai adana 2-3% na zirga-zirga, zai rage adadin masu bayarwa na farko da 1-2% kuma zai rage jinkiri kafin samuwar shigar da 2%.
Don takamaiman shafuka, canje-canje sun fi bayyane. Misali, bawa ragowar lodi na YouTube to zai rage bayanan da aka zazzage da kusan 500 KB, Instagram - ta 100 KB, Spotify - 500 KB, Facebook - 400 KB.
Musamman, yin amfani da youtube toshe ragon ɗorawa akan Chrome.com ya ba da damar wayoyin hannu don rage lokacin jiran jiran shafin don fara hulɗa har zuwa sakan 10 kuma girman lambar JavaScript da farko an ɗora a 511 KB.
Wani canji an ƙara shi zuwa tushen lambar mai bincike kuma hakan zai kasance a bayyane a cikin Chrome daga sigar 86 shine aikin a kashe nakasa cikakke don siffofin shigarwa akan shafukan da aka loda akan HTTPS amma aika bayanai akan HTTP.
An aiwatar da wannan ne saboda takaddun tabbatar da autofill a shafukan da aka buɗe ta hanyar HTTP an kashe su a cikin Chrome da Firefox na dogon lokaci, amma har yanzu, buɗe shafi tare da fom ta HTTPS ko HTTP sun zama alamar cire haɗin alamar, yanzu za a ɗauki ɓoyayyen ɓoye cikin asusu yayin gabatar da bayanai ga mai sarrafa siffofin. Hakanan, an ƙara sabon faɗakarwa ga Chrome don sanar da mai amfani don aika cikakkun bayanai ta hanyar hanyar sadarwar da ba a ɓoye ta ba.
A halin yanzu wannan fasalin za a iya kunna shi a cikin sigar Canary a cikin "chrome: // tutoci # gaurayayyun-siffofin-a kashe-autofill".
Bugu da ƙari wani canji abin da ake tsammani don Chrome 86 shine kawar da alamar gwaji, wanda ke ba ka damar nuna abu a cikin mahallin mahallin don nuna cikakken URL a cikin adireshin adireshin.
A kashi "Kullum nuna cikakken URL" zai kasance a cikin menu na mahallin ta tsohuwa, ba buƙatar canza saituna game da: shafi tutoci. Ana iya kallon cikakken URL ɗin ta danna sau biyu a sandar adireshin.
Ka tuna cewa a cikin Chrome 69, Google sunyi gwaji don ɓoye "https: //", "http: //" da "www" a cikin adireshin adireshin. Attemptoƙarin farko bai yi nasara ba kuma an soke ɓoyewar. Gwaje-gwaje da suka biyo baya sun ci gaba kuma a cikin Chrome 76, ta tsohuwa, adireshin ya fara nunawa ba tare da yarjejeniyar www da subdomain ba, kuma a cikin Chrome 79 an cire saitin don dawo da tsohuwar halayen.
Bayan rashin gamsuwa da mai amfani, an ƙara sabon tutar gwaji a cikin Chrome 86, yana ƙara abu a cikin menu na mahallin don ɓata ɓoyewa da nuna cikakken URL a cikin duk yanayin.