Sunaina Sharma

Okay. So I do have completely 9 years of experience in PHP development, including, uh, uh, PHP and its various frameworks and changes like, um, WordPress, OpenCart, voice commands, coding letter. These type of frameworks I have worked, uh, and that includes our SEO website and, uh, ecommerce website and various, uh, uh, which involves tasks related to all performance, like, um, AppSumital, SEO SEO related performance task, pages optimization, uh, payment gateway integration, shipping APIs integration, and subscription modification and integration. This type of works, I have an and worked in, uh, 4 different type of organization. And, uh, my last organization was founded in which I have worked, um, November, uh, 2023. And, uh, currently, I'm working as a freelancer developer with the solutions private limited. That's off my side.

Consistent UX. That is twice when developing a responsive website theme. Okay. So, uh, in order to maintain the consistency of, uh, UI UX, uh, on various devices, uh, the respective media CSS, uh, are, uh, I used to, uh, write the respective media for the different different devices. Like, if I am using, uh, uh, like, uh, we can make make a preload of first reporting it. And for that, if I'm using a different image for desktop and different for the mobile, then I will, uh, make that preload according to the screen dimension. Like, uh, the max 767 will be for the mobile devices and, uh, like, for the max, 1 minimum 120, uh, minimum 1 768 to, uh, like, 1,024 pixels will be the desktop desktop. And according the and in the same way, the media CSS for respective images page and the containers are used to write and, um, design behave accordingly.

Do the first step to debug a WordPress plugin that is composing performances issues. Okay. Causing the performance issue. So, uh, in order to debug that, if that plug in is causing the performance issue or or not, then first thing we'll check, uh, if the their respective CSS and JS files are calling on the specific page. Like, if, um, like, if their functionality is not recording through the website, only the one page that is using its functionality, then it's sales and c s respective JS and CSS file should be called in that particular page only, not only the complete website. And, uh, if the that JS CSS files are not recorded, uh, uh, required in our first report, then we'll make that defer and, uh, either or defer or we can, uh, call that JS or CSS file on scroll of the page. Like, if they are not recording the first report, they can we can make them on scroll. And other thing we can do, like, we can, uh, minify that CSS and JS files if required. And, uh, we can use different, uh, plugins to optimize our performance, like, uh, used SEO and our sense there. These type of, uh, WordPress plugins are there. And, uh, 1 step to debug. Yeah. In the next step, uh, in the network tab, we will also see that, uh, how much load they are, um, taking and how much time that that CS and CSS and plug in files are taking to load. And, uh, we can accordingly preload, defer, and, uh, may move them once more as per the requirement. But we can also call that plug in once, uh, according to the specific template condition or specific page conditions. That's all.

A filter for you to optimize a work beside slow time, at the servers and the code level. Okay? At the service, uh, at the server, the to optimize at the service level to optimize the load, and, uh, we can use the different type of caches, like CD and cash cache, mem cache. These type of cache cache, we can use too, and, uh, we can enable the gzip compression to make the, uh, things load faster, and the compressed objects will take the lesser time too, and it will reduce the load time. These are the server levels. And in the code level, we can do that. We can we can reduce the image sizes, the the images which are taking more time. We for all of these, uh, we can firstly, uh, we can do parts like in one part, we can, uh, optimize the all the images. Like, we can add height with 2 specific images so that that specific container will be fixed, and it will, uh, not, uh, it will decrease the LCP of the page. And, um, also, we can, uh, compress the images. If images are heavy in size, we can compress, and we can use, uh, lazy load for the images which are not required in the first report and preload for the images which are required, uh, in the first report. These were, uh, the for the images perspective and the rest are part of, like, JS and CSS file. If, uh, j for the CSS file, we will many many find the CSS file, and we will remove the, uh, unused CSS file, which is, uh, we will remove the unused code, uh, um, unassisted code from the JS CSS file feature not required in that specific page or that specific template. We will have to filter out that and, uh, minify the CSS file. We can also use sales form, uh, the CSS of, uh, unification and its calling. And if, uh, that if any particular CSS file is not required in the first group, that we can, um, we can make them on scroll of the page. If anything is not regarding the header part, we can make them do the call the in the photo also. And, uh, third party is JS. JS, we can we can remove the unwanted, uh, JS code from the, uh, files. And, uh, secondly, we can remove the, JS, uh, we can remove the JS code from the header and move that to the footer if that is not required in the, uh, first view port. And we can minify the, uh, JS files. And, uh, if if jQuery in if, uh, we can also remove the jQuery dependency and make them all scroll. If in the, uh, first throughput, uh, means, uh, there is no dependency on jQuery, like, we are not using anything which, uh, which we have to call jQuery. So we can move the jQuery on, uh, on scroll. And we can also do the one thing, like, if our, um, page is not require require requiring jQuery, then we can move the, uh, code to the change the code to the JavaScript also. And that's

Piece of jquery paste plugin. Jquery the factoid piece of jquery based plugin code to use for any last JavaScript for performance. Three factory piece of Jquery based plugin. What to use? Okay. So in that, we can do one thing. Uh, like, if, uh, this, uh, that is, like, if that plug in is using any specific jQuery based file, then we can do one thing. We can, uh, customize that specific file. We will keep the file as file name as it is, but we can, uh, customize the, uh, that code, uh, according to the vanilla JavaScript. And so that calling and everything will be same, classes and call and events will be the same. Only the core part will be changed. Dependency will be removed, and the the j JS code will be replaced in in place of that, and that will work. Uh, Yeah. Means that will work fine because, uh, I have done one of the implementation in one of the plug in, which was using. Like, uh, the plug in was k k star rating, which was using the. And check only dependency, we have to remove because it was causing the performance issue and making the low, uh, increasing the load time. So for that, I have, uh, converted the check for recording to the JavaScript, and, uh, all the events and code of is converted to the JavaScript, and it worked fine. There was no issue. Just we have to keep in mind while we are upgrading the plug in. So we have to modify the, uh, code again accordingly.

How would you approach version controlling in a new environment using it while developing in the while developing WordPress plugin? Okay. So version controlling, uh, in the Git, uh, uh, in the WordPress, we mainly, uh, we have to mainly drag the wp content folder, uh, with the projects which I will working. Uh, in the kit, we have kept only the WP content folder, which includes, uh, any other folder like WP admin and WP includes was not on the gate. And, uh, okay. So, uh, while we are developing the plug in, So we can do 1 while we are developing a plug in. So, uh, while we are developing a plug in, controlling a team environment using it while we are developing WordPress plugin. Okay. So we can do one thing. While we are developing a plugin, we can do one thing. We can create we can, uh, create us a branch. If, uh, a branch, then we can create a branch, uh, and then we can create a work occur in that specific branch. And, uh, if, uh, and and, uh, other developer can create a separate branch, and we can, uh, can merge that branch together on the master environment. Or before merging to the master environment, uh, we can merge it and, uh, merge that both branch in our local and verify the things. And if, uh, there is no issue and things are working fine, then we will merge that, uh, club branch, uh, that, uh, like, if if we are if there is a branch and if there is a b branch, and if we have merged our code, like developer a and developer b merge their code in the branch a. And after verification and all the things, then only we will merge that a branch in the master and the master branch and verify the code. Like, master branch is our dev environment. I'm considering that dev environment, and then we'll merge that to the dev environment and verify the things there.

And, like, what it does, uh, endpoint out any potential security flaws. New is a delight. Given this feature function, identify what is does it matter? Square credential. Username is this and password is this. Okay. Security, uh, flaw is there is that, uh, we are directly verifying the password password field. We are directing, um, directly verify in the database. It shows, like, password is not encrypted in the form. It is saved directly as a text in the database. So before, um, the password should always be in the encrypted form, like m d 5 or any other encryption method we can use here so that password should not be visible to any of the it should not be visible to the in the database or directly. In this way, like, all the password will show the password as to, like, a, b, c, d. It should be always in the encrypted form.

This, please, CSS number that is supposed to style a finding message. What is wrong with it? And how how would you correct the warning message by? That is supposed to style a warning message. Okay. What is wrong with it? Icon color is red. Text color is white. Font page is font. Font feed. Font. Uh, font feed, we can also specify in numbers like 100, 200, 300, 400. We can also specify in that field. And color is font color white. Background color, we are using that, and it will display font color as a white. In the color, we can, uh, in in place of color, we can use font color. That would be more specific to specify the font color. Okay. Uh, Yeah. How are they? Uh, the class name which we have used for warning is is it should be, uh, means there should not be space within the last name, like, warning space message. It it this is the this is not a correct way. It should it may be warning underscore message, warning without space message. The name should be in this way.

Okay. Implement person control and feature branch for a complex frame with the multiple developers. Okay. Fine. If we, uh, when we are implementing the person controlling that are like, we have implemented git in the production environment, then, uh, we have a a branch like staging. We have a branch like dev environment, which is master, then, uh, we have to keep all the environments sync. And, uh, in the first step, we'll we'll take the pull of production branch that is our production environment to staging environment and also to the master environment. And while, uh, uh, say, uh, team is working, then there are different everyone is working on the different task, then there should be different ticket for the diff sorry, different branch for the different task. Uh, as soon as the developer complete the task, verify the task, that specific branch should get merged to the master environment. And after and same as with other developer that, uh, as soon as they complete the task, then that will be merged to the master environment. And, uh, like, if we are planning to, uh, when we are planning to release, then, uh, that, uh, only those changes should get merged to the dev environment, uh, master environment, uh, which we have to take in the release. And while we are, um, like, all the developers have done, they are working the master environment, and we are planning to release them. We will merge all the, uh, all the code of master batch to the staging because our, um, our master is already synced with the staging and production environment. And now our master environment is containing the code which our developer had has worked on the different task. So only that code will be merged to the staging environment. And before merging, we will verify we will reverify if our branch, uh, that particular the code we are going to match to the staging environment, uh, that, uh, that is containing our changes, our, uh, respective task, uh, changes only, or it is containing some extra code. We have to verify the format, and then we'll reverse to the staging environment. And same will happen while we are doing the release from staging to the production. The staging branch should get will get merged to that. APR will be created. Pull request will be created from staging to production. This is the this is related to the normal release. If you are working on CICD release, then we will create, uh, we will prefer to create a sprint branch. Like, uh, like, we have created for a specific one. Like, it is a 7 v 1 sprint, then we'll create a 7 one sprint branch, and all, uh, tickets will get once, uh, specific task branch will get merged to the master environment. And before, uh, while we are developing the, um, deploying the changes to the staging staging environment, then we will merge all, uh, we will merge all those branches to the, uh, our sprint branch, and only the sprint branch will get merged to the staging of the production environment. That's all.

Introduce my app to ensure a simple sound from with you. 1 plus 1 do not. Introduce my my screenshot as sync. Calls, fitting in WordPress plugin, do not affect me. Okay. So we define the j s j s as async to improve our, uh, uh, async or therefore, we define, uh, either we define the, uh, JS as async or the in order to improve the page performance and making them to load after, uh, not initially on Facebook, but after, like, uh, downloading of all the after downloading of all the content or, uh, doc, um, down completion of the down download and in my years to ensure. Okay. So while we are, uh, making, uh, uh, any JS, uh, a sync or, uh, uh, then, uh, we Okay. Uh, while we are planning to make any JS as a async, then we have to, uh, we have to, uh, firstly go through their functionality that, uh, if we are making any specific JS as a async, then it should not impact the page. Like, uh, if that JS is required on initially on page load, then, uh, it will give an error, and, uh, the the functionality will stop working. So we have to work in a way we have to either make the part their specific part of the group. Like, if we we can do we can divide the JSON parts of code. Like, if, um, half part is required on page load and rest of the part is, uh, after after the completion of page load, after the download download, then we can divide them part in the part. Like, we can move the rest of the pattern in the, uh, footer and make them, uh, async. And the the part which is required initially, we can make that, uh, we can do call that in header and, uh, without making that async. And it will, uh, not impact our performance and, uh, also, uh, the functionality will work fine. Functionality will work fine.

Dashboard into a WordPress tool using our SDK and front end technology. Okay. So in order to develop a, uh, dashboard, dashboard will, uh, fetch the data from different different, uh, like, our in house. You do have. Okay. So, uh, uh, if we are planning to implement a dashboard in the WordPress plugin using okay. So we we we can do, uh, we can create a custom plug in. Into a custom plug in, we can, uh, create a a menu item using add menu add menu hooks and, uh, uh, and create that, uh, a specific page for that, which will and, uh, like, the while we are creating a plug in, then we will use activation hook, deactivation hook for for implementing the feature, like, uh, on activation, what will be happen. And on the activation, what will happen, we can define there. And then, uh, we will we will call a specific, uh, we will add a function to call, uh, that specific page data and in which we will call the restful APIs for, uh, you know, fetching the data as that specific API and and and the front end technology and design the page, uh, uh, and design the page according to, uh, like dashboard. Dashboard will contain that as a report, like, uh, from the different different ever in house, uh, WordPress daily also and from the rest API also, and it will get, uh, it will get, uh, updated. Uh, it will it gets, uh, in updated in sync whenever the data will get updated in the rest API. And, uh, the page URL, uh, will be defined Page URL will be defined in our WordPress plug in, uh, like, with the function name, and data will be updated and deleted and modified accordingly, uh, according to the restful, uh, restful API. But what link we get from there. And, Like, uh, it may be for example, they will provide us in the rest of API. They will provide us endpoints, uh, for specific data collection, and we'll hit those endpoints either from curl or any other way in PHP and then fetch the data accordingly. That's all.