1.6 sec in total
218 ms
1.3 sec
134 ms
Click here to check amazing Concern ROZEE content for Pakistan. Otherwise, check out these important facts you probably never knew about concern.rozee.pk
Find all latest job openings in ROZEE.PK Company. Register now and apply for all listed jobs in ROZEE.PK.
Visit concern.rozee.pkWe analyzed Concern.rozee.pk page load time and found that the first response time was 218 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
concern.rozee.pk performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value11.6 s
0/100
25%
Value8.3 s
19/100
10%
Value750 ms
39/100
30%
Value0
100/100
15%
Value11.2 s
20/100
10%
218 ms
160 ms
162 ms
31 ms
156 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 82% of them (27 requests) were addressed to the original Concern.rozee.pk, 9% (3 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (652 ms) belongs to the original domain Concern.rozee.pk.
Page size can be reduced by 267.5 kB (71%)
379.3 kB
111.7 kB
In fact, the total size of Concern.rozee.pk main page is 379.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 245.5 kB which makes up the majority of the site volume.
Potential reduce by 5.8 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 5.8 kB or 66% of the original size.
Potential reduce by 175.0 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, Concern ROZEE needs image optimization as it can save up to 175.0 kB or 71% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 51.5 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 51.5 kB or 63% of the original size.
Potential reduce by 35.3 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. Concern.rozee.pk needs all CSS files to be minified and compressed as it can save up to 35.3 kB or 81% of the original size.
Number of requests can be reduced by 18 (58%)
31
13
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Concern ROZEE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
concern.rozee.pk
218 ms
concern-worldwide.css
160 ms
cmn.css
162 ms
jquery.min.js
31 ms
custom-jq.js
156 ms
misc.js
180 ms
facebox.js
179 ms
responsiveslides.min.js
182 ms
facebox.css
318 ms
ga.js
31 ms
__utm.gif
12 ms
if.php
194 ms
shado_R.jpg
88 ms
shado_L.jpg
89 ms
logo.jpg
244 ms
pep_mnu.jpg
244 ms
men-bg.jpg
165 ms
line.png
174 ms
btn_apply.gif
249 ms
pdf.jpg
652 ms
rozee-pyip.png
335 ms
concern-worldwide_bul1.gif
312 ms
closelabel.gif
373 ms
loading.gif
393 ms
tl1.gif
386 ms
b1.gif
465 ms
tr1.gif
479 ms
bl1.gif
533 ms
br1.gif
547 ms
login-hor.css
393 ms
logo-chabee-white.gif
142 ms
logo-chabee1.gif
82 ms
__utm.gif
12 ms
concern.rozee.pk accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
concern.rozee.pk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
concern.rozee.pk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Concern.rozee.pk can be misinterpreted by Google and other search engines. Our service has detected that English 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 Concern.rozee.pk 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.
concern.rozee.pk
Open Graph description is not detected on the main page of Concern ROZEE. 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: