14.9 sec in total
26 ms
13.8 sec
1.1 sec
Welcome to pi.works homepage info - get ready to check P I best content right away, or after learning these important things about pi.works
P.I. Works is the leading provider of mobile network planning, management and optimization solutions worldwide.
Visit pi.worksWe analyzed Pi.works page load time and found that the first response time was 26 ms and then it took 14.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pi.works performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value8.5 s
2/100
25%
Value15.0 s
1/100
10%
Value2,240 ms
6/100
30%
Value0.014
100/100
15%
Value17.9 s
4/100
10%
26 ms
3948 ms
105 ms
650 ms
734 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pi.works, 82% (112 requests) were made to Piworks.net and 3% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Piworks.net.
Page size can be reduced by 1.5 MB (27%)
5.5 MB
4.0 MB
In fact, the total size of Pi.works main page is 5.5 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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 181.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. This page needs HTML code to be minified as it can gain 41.5 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 181.1 kB or 84% of the original size.
Potential reduce by 1.1 MB
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, P I needs image optimization as it can save up to 1.1 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 157.8 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 157.8 kB or 25% of the original size.
Potential reduce by 35.1 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. Pi.works needs all CSS files to be minified and compressed as it can save up to 35.1 kB or 34% of the original size.
Number of requests can be reduced by 49 (38%)
129
80
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of P I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pi.works
26 ms
piworks.net
3948 ms
gtm.js
105 ms
animate.min.css
650 ms
bootstrap.min.css
734 ms
global.css
787 ms
css2
45 ms
css2
57 ms
main.css
597 ms
mobile.css
662 ms
home.css
688 ms
home_mobile.css
980 ms
jquery-ui.min.css
45 ms
lightgallery.css
1237 ms
home-inner.css
1070 ms
home-inner-mobile.css
1127 ms
logo-evoplatform.svg
811 ms
db7a8ff22b514a5d82243a89767a7ada-ProductsBanner.jpg
1504 ms
jquery.min.js
1436 ms
bootstrap.min.js
1477 ms
jquery.bxslider.min.js
1542 ms
owl.carousel.min.js
1609 ms
gaugeMeter-2.0.0.min.js
1725 ms
wow.min.js
1803 ms
particles.js
1968 ms
global.js
1984 ms
angular.min.js
44 ms
angular-toastr.tpls.min.js
1969 ms
angular-animate.min.js
50 ms
angular-aria.min.js
53 ms
angular-messages.min.js
55 ms
angular-sanitize.min.js
292 ms
app.min.js
2041 ms
api.js
59 ms
main.js
2185 ms
lightgallery.min.js
2271 ms
lg-video.js
2347 ms
lg-autoplay.js
2335 ms
waypoints.min.js
2371 ms
lottie.min.js
2842 ms
icon-animation.js
2941 ms
home.js
2631 ms
home-inner.js
2709 ms
cc6b3fe948e44311a48d570041a1cd78-ServicesBanner.jpg
3111 ms
d9ed53e37d4c49bfa5dc71a92b86ba65-SolutionsBanner.jpg
3064 ms
84ed3130892844988117519fc19eb44c-AboutBanner.jpg
3122 ms
443c05bcbd954624a236145b5d79576d-CareerBanner.jpg
2923 ms
1e72480633da435b8258a83036154bfd-InlineImage.png
3752 ms
analytics.js
23 ms
insight.min.js
111 ms
collect
15 ms
collect
36 ms
js
75 ms
insight.old.min.js
9 ms
ga-audiences
23 ms
9b414eef0bce4901b90292e364363d5d-Image.png
2723 ms
e16e72d3c5604931a1768065ad4c9a46-Image.png
2880 ms
00548049c0fd4589a34c838d2229503e-Image.png
2956 ms
e847373cf0494a72aefd1e1a992c1aa6-Image.png
3008 ms
be6d230708a84d4bb4cb92a70877876e-Image.png
2591 ms
1eaecaf8dd54401a801ec8a326ceeb15-Image.png
2889 ms
11602079714e4035b582367e2ac778c1-Image.png
2903 ms
e4daed44fd84432fa555c0870f2af19b-Image.png
3051 ms
85fe93aa192b408c8ea6cc4f90b91a5d-Image.png
2940 ms
b6086a451cd346e984da2f116c427c28-Image.png
2940 ms
dcc3b994eb7f473ebcfd79fb077d8b80-Image.png
2724 ms
S6uyw4BMUTPHvxk.ttf
21 ms
S6u9w4BMUTPHh7USew8.ttf
27 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntA.ttf
39 ms
pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GiClntA.ttf
40 ms
HelveticaNeueLTPro-Md.woff
2823 ms
HelveticaNeueLTPro-Lt.woff
2965 ms
19888205ceaa4904aff0cf047fc2747c-Image.png
2883 ms
bfe94f4d912648e0885a8db97d2972ef-ImageDark.png
2871 ms
70c854ea9fd74845bde38f0bace96440-ImageDark.png
3395 ms
975ba04e719f41bda2d85a75e57d30b2-ImageDark.png
3037 ms
83c96efc1c724d30994a03d08f533103-ImageDark.png
2837 ms
df29aff997874b038000557ea2c49984-ImageDark.png
2782 ms
daa6a627026a49cf88c98facd51f512a-ImageDark.png
2874 ms
3d0375fdba0440d6b2b558cbb38e49c7-ImageDark.png
2998 ms
recaptcha__en.js
29 ms
f1f66def2b6347d7bbd87826c4f1a1d8-ImageDark.png
2998 ms
3a68e60e09a9406f985a643a364672c4-ImageDark.png
2673 ms
9e70b7f6488646859672806d3fa2b80c-ImageDark.jpg
2702 ms
6cd08e5f5c874b2c9fae47710a9c846e-ImageDark.png
3098 ms
8241b41bf4944ed097bb25d8dc763329-ImageDark.png
3071 ms
86d9d930ae7a49c3be44f1548678fb50-ImageDark.png
3077 ms
5836cebe892142188ac4e0aa0f003321-ImageDark.png
3018 ms
adda2d94154c44ee9602a7bfc4010dc4-ImageDark.png
2991 ms
ae6ea933fdec439283f1eee698b656b3-ImageDark.png
3664 ms
24f7fe8c2cbb44b89a86086094572e15-ImageDark.jpg
2954 ms
hotjar-766083.js
194 ms
00d6e9d1e5dd44099255593dbb423261-HighlightImage.jpg
2940 ms
afd42a3a452543e0b9c3273dc4dbac8c-HighlightImage.jpg
2962 ms
c2f2b60f58444199b01e41638a58a235-HighlightImage.jpg
3437 ms
ae843587d67f4f9f9ae1e40be9065bf2-HighlightImage.png
3304 ms
modules.84f80a92c39bbd76564a.js
18 ms
5fb519b3ac284939813214c7adffaf7e-HighlightImage.jpg
3438 ms
a95a875aaad94139accbe429d7813796-HighlightImage.jpg
3173 ms
newsletter.svg
2898 ms
EXA.svg
3266 ms
vpm.svg
3348 ms
EXP.svg
3248 ms
CFG.svg
3227 ms
managedservices.png
3164 ms
professionalservices.png
3124 ms
trainingservices.png
3234 ms
service%20operations%20center.png
3236 ms
special%20event%20management.png
3297 ms
volte.png
3098 ms
iot%20opt.png
3142 ms
hetnet.png
3111 ms
spectrum%20reframing.png
2920 ms
driveless%20tuning.png
3027 ms
smart%20energy%20saving.png
2991 ms
news.png
2982 ms
events.png
2743 ms
blog.png
3741 ms
white%20papers.png
3711 ms
36db886f5c624ca3aa8c80c4d1bd6d7b-InsightBanner.png
3259 ms
company.png
3020 ms
technology.png
3084 ms
customers.png
2706 ms
partners.png
2996 ms
life%20at%20piworks.png
3273 ms
our%20values.png
2842 ms
job%20opportunities.png
2681 ms
09916a1766c9447a90d6d7399d2a5d5a-InlineImage.jpg
3108 ms
piworks_5G_logo_white2.svg
3212 ms
icon-search.png
2830 ms
icon-mail.png
3224 ms
icon-calendar.png
2363 ms
icn-linkedin.svg
2642 ms
icn-facebook.svg
2799 ms
icn-twitter.svg
2679 ms
icn-youtube.svg
2615 ms
icn-instagram.svg
2660 ms
pi.works accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
pi.works 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
Page has valid source maps
pi.works SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Pi.works 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 Pi.works 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.
pi.works
Open Graph data is detected on the main page of P I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: