Tools & Wizards About Us
prohq.ru screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

prohq.ru

Удаленная работа (free lance) | биржа фриланса Prohq | работа на дому для фрилансеров, поиск удаленной работы - Prohq

Page Load Speed

4.6 sec in total

First Response

526 ms

Resources Loaded

3.8 sec

Page Rendered

273 ms

prohq.ru screenshot

About Website

Click here to check amazing Prohq content for Russia. Otherwise, check out these important facts you probably never knew about prohq.ru

Поиск удаленной работы на дому, биржа фриланса Prohq – поиск фрилансеров по специализациям и отраслям

Visit prohq.ru

Key Findings

We analyzed Prohq.ru page load time and found that the first response time was 526 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

prohq.ru performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

prohq.ru

526 ms

www.prohq.ru

528 ms

ga_exp.js

6 ms

front_page-e6befc48266fae40118b25395f29bb7b.css

887 ms

conversion.js

69 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 69% of them (31 requests) were addressed to the original Prohq.ru, 9% (4 requests) were made to Gdeslon.ru and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Prohq.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (48%)

Content Size

2.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prohq.ru main page is 2.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 22.1 kB

  • Original 31.2 kB
  • After minification 28.4 kB
  • After compression 9.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.1 kB or 71% of the original size.

Image Optimization

-26%

Potential reduce by 286.1 kB

  • Original 1.1 MB
  • After minification 813.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Prohq needs image optimization as it can save up to 286.1 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 571.0 kB

  • Original 854.0 kB
  • After minification 853.7 kB
  • After compression 283.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 571.0 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 159.6 kB

  • Original 189.4 kB
  • After minification 188.6 kB
  • After compression 29.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Prohq.ru needs all CSS files to be minified and compressed as it can save up to 159.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (21%)

Requests Now

39

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prohq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

prohq.ru

prohq.ru

526 ms

www.prohq.ru

www.prohq.ru

528 ms

ga_exp.js

ga_exp.js

6 ms

front_page-e6befc48266fae40118b25395f29bb7b.css

front_page-e6befc48266fae40118b25395f29bb7b.css

887 ms

conversion.js

conversion.js

69 ms

landing.js

landing.js

259 ms

watch.js

watch.js

0 ms

application-215e77a1b747ac68bb7cf8889a651ca3.js

application-215e77a1b747ac68bb7cf8889a651ca3.js

2215 ms

landing.js

landing.js

569 ms

bg-a528bb9fe5cc18b2c666abad6381124f.png

bg-a528bb9fe5cc18b2c666abad6381124f.png

128 ms

logo-06ffae2be77d03c43c57e94a92130e4e.png

logo-06ffae2be77d03c43c57e94a92130e4e.png

255 ms

icons-07dfa973c21b3d940876f5127ae93428.png

icons-07dfa973c21b3d940876f5127ae93428.png

637 ms

yana-on-cloud2-6e831718d8ada2a7af4e29e7ecefbb45.png

yana-on-cloud2-6e831718d8ada2a7af4e29e7ecefbb45.png

1565 ms

hr940down-821ae5c6fcddec1e59d0cb12b14aea47.png

hr940down-821ae5c6fcddec1e59d0cb12b14aea47.png

654 ms

digits-11202811a8fb47cbbac7063297feb922.png

digits-11202811a8fb47cbbac7063297feb922.png

262 ms

arrows-saeb8034515-5741deaed3aa2158043819568e5c5bdb.png

arrows-saeb8034515-5741deaed3aa2158043819568e5c5bdb.png

381 ms

hq-footer-mini-c5d2d47b424be444ec71888cd6671e77.png

hq-footer-mini-c5d2d47b424be444ec71888cd6671e77.png

393 ms

main-footer-fin-630c0085ae08643f51765c2d3b133d91.png

main-footer-fin-630c0085ae08643f51765c2d3b133d91.png

760 ms

ajax-loader-67aff06a40cc4bc80a7121567749b606.gif

ajax-loader-67aff06a40cc4bc80a7121567749b606.gif

524 ms

PTN57F-webfont-ad7b0c802e84a328b58c25f6cdd0d8ca.woff

PTN57F-webfont-ad7b0c802e84a328b58c25f6cdd0d8ca.woff

1133 ms

PTN77F-webfont-36b6c71fa5b93e7026e154c72e39d866.woff

PTN77F-webfont-36b6c71fa5b93e7026e154c72e39d866.woff

844 ms

PTC55F-webfont-8bb9468b4a903d7020171aa6a7ce6288.woff

PTC55F-webfont-8bb9468b4a903d7020171aa6a7ce6288.woff

868 ms

PTC75F-webfont-d034d1e32c0f840e54840da214d19cdd.woff

PTC75F-webfont-d034d1e32c0f840e54840da214d19cdd.woff

968 ms

PTS55F-webfont-806c7388d1acead84b555dd0d099aa16.woff

PTS55F-webfont-806c7388d1acead84b555dd0d099aa16.woff

1100 ms

PTS75F-webfont-06a29bd6f029a9d6c688d49ddba6cc55.woff

PTS75F-webfont-06a29bd6f029a9d6c688d49ddba6cc55.woff

1130 ms

PTS76F-webfont-6aafdfbd17f12bfca7b42aaaf98a258c.woff

PTS76F-webfont-6aafdfbd17f12bfca7b42aaaf98a258c.woff

1300 ms

PTS56F-webfont-30785e3a51bbc2096012f2648e61b2be.woff

PTS56F-webfont-30785e3a51bbc2096012f2648e61b2be.woff

1358 ms

42 ms

landing-backend.js

landing-backend.js

129 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

15 ms

29 ms

32 ms

landing-backend.js

landing-backend.js

136 ms

gsclick.js

gsclick.js

516 ms

farcloud1-8-eec025ea0a67ef3c7c85c5274c53939a.png

farcloud1-8-eec025ea0a67ef3c7c85c5274c53939a.png

131 ms

farcloud2-8-d8fdd4592101775518d2e1d91723c7dd.png

farcloud2-8-d8fdd4592101775518d2e1d91723c7dd.png

129 ms

farcloud3-8-cd58c2e82fa6ef8e1c9ddf0479ec575f.png

farcloud3-8-cd58c2e82fa6ef8e1c9ddf0479ec575f.png

262 ms

farcloud4-8-13b7b3b812a6c1e05369686651ce1e08.png

farcloud4-8-13b7b3b812a6c1e05369686651ce1e08.png

130 ms

cloud-mid1-8-75545d9908f0e92067532e7907a05545.png

cloud-mid1-8-75545d9908f0e92067532e7907a05545.png

132 ms

cloud-mid2-8-3a734b17033a501dbbb0a41741a76240.png

cloud-mid2-8-3a734b17033a501dbbb0a41741a76240.png

159 ms

cloud-mid3-8.png

cloud-mid3-8.png

255 ms

cc2-09ff7e69c1c7e96e4b1ef47b0fc4c9e0.png

cc2-09ff7e69c1c7e96e4b1ef47b0fc4c9e0.png

383 ms

cc1-816535875fb4fd5e23cfb01f5db2f28b.png

cc1-816535875fb4fd5e23cfb01f5db2f28b.png

392 ms

nr-100.js

nr-100.js

45 ms

Accessibility Review

prohq.ru accessibility score

81

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

prohq.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

prohq.ru SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prohq.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prohq.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

prohq.ru

Open Graph description is not detected on the main page of Prohq. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: