3.8 sec in total
350 ms
2.9 sec
460 ms
Visit greenshark.pk now to see the best up-to-date Greenshark content and also check out these interesting facts you probably never knew about greenshark.pk
Welcome To GREEN SHARK - We offer a wide range of Software, ERP, CRM, Web Sites, Online Stores, Software, Free Domain Registration & Web Hosting
Visit greenshark.pkWe analyzed Greenshark.pk page load time and found that the first response time was 350 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
greenshark.pk performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value11.7 s
0/100
25%
Value11.6 s
4/100
10%
Value630 ms
47/100
30%
Value0.114
86/100
15%
Value11.4 s
19/100
10%
350 ms
767 ms
179 ms
532 ms
442 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 48% of them (41 requests) were addressed to the original Greenshark.pk, 43% (37 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Wpdemo.archiwp.com. The less responsive or slowest element that took the longest time to load (888 ms) belongs to the original domain Greenshark.pk.
Page size can be reduced by 776.5 kB (26%)
2.9 MB
2.2 MB
In fact, the total size of Greenshark.pk main page is 2.9 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. Only a small number of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 606.0 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 606.0 kB or 83% of the original size.
Potential reduce by 170.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. Greenshark images are well optimized though.
Potential reduce by 543 B
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. This website has mostly compressed JavaScripts.
We found no issues to fix!
41
41
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenshark. According to our analytics all requests are already optimized.
greenshark.pk
350 ms
www.greenshark.pk
767 ms
wpo-minify-header-dd5e180f.min.js
179 ms
wpo-minify-footer-e0d6775a.min.js
532 ms
wpo-minify-footer-45b20759.min.js
442 ms
css2
40 ms
logo-home-9.png
270 ms
bg-header-home4.png
267 ms
shape1-home4.png
121 ms
gg-rating.png
122 ms
shape2-home4.png
125 ms
shape4-home4.png
124 ms
shape3-home4.png
125 ms
green-shark-2.png
186 ms
green-shark2.png
169 ms
close.png
322 ms
green-shark.png
335 ms
green-shark2.png
366 ms
green-shark-home.png
664 ms
green-shark-8.png
602 ms
zamzamfood.co_.uk_.jpg
547 ms
02-sanzly.jpg
601 ms
04-mirmed.jpg
452 ms
zummcargo.co_.uk_.jpg
454 ms
theglamfab.jpg
549 ms
akmalindustry-1.jpg
599 ms
marfas.pk_.jpg
603 ms
shafiqueempire.jpg
662 ms
mrjeans.com_.pk_.jpg
665 ms
airmarkint-1.jpg
664 ms
imageimpex.jpg
665 ms
06-map.jpg
738 ms
07-mafzal.jpg
711 ms
17.jpg
736 ms
shafiqueempire-1.jpg
738 ms
jp-leather.jpg
739 ms
23.jpg
739 ms
12-boxmax.jpg
803 ms
icellularrepair.jpg
802 ms
highlandkiltscompany.pk_.jpg
818 ms
goinggloves.jpg
818 ms
a2zautorepair.us_-1.jpg
888 ms
fa-brands-400.woff
794 ms
fa-brands-400.woff
753 ms
Flaticon.svg
794 ms
Flaticon.woff
794 ms
fa-solid-900.woff
794 ms
fa-solid-900.woff
830 ms
fa-regular-400.woff
791 ms
RrQCbohi_ic6B3yVSzGBrMx6ZI_cy1A6Ok2ML7hwVrbacYVEjIU.ttf
81 ms
RrQCbohi_ic6B3yVSzGBrMx6ZI_cy1A6Ok2ML4pwVrbacYVEjIU.ttf
131 ms
RrQCbohi_ic6B3yVSzGBrMx6ZI_cy1A6Ok2ML-ZwVrbacYVEjIU.ttf
281 ms
RrQCbohi_ic6B3yVSzGBrMx6ZI_cy1A6Ok2ML2Z3VrbacYVEjIU.ttf
170 ms
RrQCbohi_ic6B3yVSzGBrMx6ZI_cy1A6Ok2ML193VrbacYVEjIU.ttf
224 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbouRckg5-Xedu38.ttf
163 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbuyRckg5-Xedu38.ttf
163 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbsWRckg5-Xedu38.ttf
166 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbrKRckg5-Xedu38.ttf
167 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbl6Wckg5-Xedu38.ttf
167 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbmyWckg5-Xedu38.ttf
167 ms
8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbjKWckg5-Xedu38.ttf
168 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVMwwz_VWZk33xGQ.ttf
223 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVGgwz_VWZk33xGQ.ttf
335 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVfQwz_VWZk33xGQ.ttf
225 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVRAwz_VWZk33xGQ.ttf
224 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVqAsz_VWZk33xGQ.ttf
224 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVmgsz_VWZk33xGQ.ttf
338 ms
8vIh7wUr0m80wwYf0QCXZzYzUoTg-CSvZX4Vlf1fe6TVxAsz_VWZk33xGQ.ttf
276 ms
KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf
269 ms
KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf
270 ms
KFOmCnqEu92Fr1Me5WZNCzc.ttf
270 ms
KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf
271 ms
KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf
273 ms
KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf
273 ms
qWc-B6yyq4P9Adr3RtoX1q6ySgbwusXwJjkOS-XEssPvRfRLYWihSw.ttf
276 ms
qWc-B6yyq4P9Adr3RtoX1q6ySgbwusXwJjkOS-XEgMPvRfRLYWihSw.ttf
333 ms
qWc-B6yyq4P9Adr3RtoX1q6ySgbwusXwJjkOS-XEbMTvRfRLYWihSw.ttf
333 ms
qWc-B6yyq4P9Adr3RtoX1q6ySgbwusXwJjkOS-XEVcTvRfRLYWihSw.ttf
451 ms
qWc-B6yyq4P9Adr3RtoX1q6ySgbwusXwJjkOS-XEMsTvRfRLYWihSw.ttf
336 ms
HhyXU5si9Om7PTHTLtCCOoxCTQ.ttf
382 ms
HhyaU5si9Om7PQlvAfKKEA.ttf
338 ms
RrQEbohi_ic6B3yVSzGBrMxQbb0jEzlRoOOLOnAzvvXQdadApIcX_Q.ttf
450 ms
RrQEbohi_ic6B3yVSzGBrMxQbb0jEzlRoOOLOnAzjPXQdadApIcX_Q.ttf
382 ms
RrQEbohi_ic6B3yVSzGBrMxQbb0jEzlRoOOLOnAz4PXQdadApIcX_Q.ttf
408 ms
RrQEbohi_ic6B3yVSzGBrMxQbb0jEzlRoOOLOnAzYPLQdadApIcX_Q.ttf
383 ms
RrQEbohi_ic6B3yVSzGBrMxQbb0jEzlRoOOLOnAzWfLQdadApIcX_Q.ttf
284 ms
greenshark.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
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
greenshark.pk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
greenshark.pk SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenshark.pk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Greenshark.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.
greenshark.pk
Open Graph description is not detected on the main page of Greenshark. 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: