Budget: 1500 UAH Deadline: 1 day
Welcome to.
I will make a guaranteed mobile 70+ , PC 90+
There is experience with similar (self-written) topics.
Budget: 1500 UAH Deadline: 1 day
Welcome to.
I will make a guaranteed mobile 70+ , PC 90+
There is experience with similar (self-written) topics.
Budget: 1000 UAH Deadline: 1 day
Good afternoon.
The site protests.
The main problems, images, scripts, fonts, lack of caching
Everything goes straightforward and quickly.
Ready to work.
Budget: 2000 UAH Deadline: 2 days
Good day, to increase the speed you need to work with images and JS, in general I can do everything!)
Budget: 3800 UAH Deadline: 3 days
Good day .I see that they tried to make optimization using the cache plugin, but this is obviously not enough.We can try to bring the download speed for mobile devices to the PageSpeed green zone.I will need access to the host and to the WordPress admin.- Before starting the test, I will perform a series of tests to determine the output state and the site’s download speed.Based on the results of the tests, I develop an optimization strategy that depends on the hosting, themes and plugins set on the site.- I make a backup of the database and files.I do my own optimization (pressing and delayed image download, font download optimization, CSS and JS scripts styles).- Re-testing the performance and functionality of the site (to make sure everything works without errors).The deadline (3 days) indicated approximately, will depend on the frequency and duration of lighting in me.But I will try to do everything as quickly as possible.If you are interested in my offer, please write in private.I will be glad to answer your questions.
Budget: 2000 UAH Deadline: 2 days
There is a great experience in accelerating sites.Pack will be 80+ to get out
Budget: 1234 UAH Deadline: 1 day
Good day .
I will start now.
We will agree on the price in person.
It is necessary to migrate a custom project from CodeIgniter 2 to Laravel 12. I will provide details in private messages.
Project The existing website is developed on Symfony. The project needs to be taken over for support, familiarize with the code, and subsequently carry out improvements. Main tasks Implement all technical recommendations from the SEO specialist according to the provided technical assignment. Make changes to the monument configurator according to a separate list of requirements. Implement the updated website design (layout and integration of the new design). Carry out further technical improvements and support for the website as needed. Expectations from the developer Familiarization with the project structure and codebase. Assessment of costs and timelines for each stage. Adherence to the existing project architecture and quality implementation of changes. Maintaining communication regarding task execution and possible technical solutions.
I want a bot for Telegram. Loading dialogues. With the help of AI, checking for potential lies. A website with advanced features. Registration, API, statistics, etc.
It is necessary to migrate the Opencart online store from PHP 7.4 to PHP 8.x. Currently, the core version is 3.0.3.8. We read that most likely the core will also need to be migrated to version 4.0 and there shouldn't be many difficulties... The functionality is mostly custom, and there are also Simple, OCFilter, Nova Poshta. We are waiting for recommendations and an approximate price. Ideally, someone who has already done similar work.
It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.