Show

Ponpare.jp ?疋瓮ぅ鵐僉璽

Need help with your SEO?
Online Status
Offline

Server IP address resolved: No
Http response code: None
Last Checked: 09/16/2019

Ponpare.jp receives about one thousand unique visitors and three thousand pageviews per day. The estimated value of ponpare.jp is sixty thousand USD. Each unique visitor makes about 2.7 pageviews on average.

Over the time ponpare.jp has been ranked as high as 5,331 in the world, while most of its traffic comes from Japan, where it reached as high as 40,156 position.

It’s good for ponpare.jp that their hosting company INFOSPHERE NTT PC Communications, Inc., JP server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time. See the list of other websites hosted by INFOSPHERE NTT PC Communications, Inc., JP.

Ponpare.jp is registered under .JP top-level domain. Check other websites in .JP zone.

At the time of the last check (November 20, 2019) ponpare.jp has an invalid SSL certificate.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust ponpare.jp is quite a safe domain.

Mobile-Friendly test indicates that ponpare.jp is well optimized for mobile and tablet devices, however website page loading time could be improved.

Global Rank
213,731
Average Load Time
1.99sec
Links In Count
294
Website Value
$59,130
Overview
Last Updated: 11/20/2019
Overall result - "ponpare.jp" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 01/12/2019
NCS "ponpare.jp" OK.

Norton ConnectSafe evaluates ponpare.jp for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 10/11/2016
GSS "ponpare.jp" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 01/09/2019
Malware not found at "ponpare.jp".
"ponpare.jp" is not a phishing page.
"ponpare.jp" does not install unwanted software.
"ponpare.jp" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 01/09/2019
SA "ponpare.jp" OK.

McAfee assesses ponpare.jp for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze ponpare.jp for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 01/09/2019
WOT "ponpare.jp" VERY GOOD.

The WOT calculates reputation of the ponpare.jp. This reputation system receives ratings from users and information from third-party sources, assesses the ponpare.jp for safety features and confirms, whether ponpare.jp is suitable for children.

SSL Information
WARNING! Certificate download error. Previous scan results are shown below.
Domain Unknown
Issuer Organization Unknown
Issuer Unknown
Algorithm Unknown
Valid form Unknown
Expiration Unknown
Signed No information
Additional Domains
Server Location
Tokyo
Tokyo
Japan
ASN Information

ASN ID: 2514
ASN Title: INFOSPHERE NTT PC Communications, Inc., JP

Last Update: 05/30/2019

% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

% Information related to 'AS2497 - AS2528'

as-block: AS2497 - AS2528
descr: JPNIC-2Byte-ASBLOCK-AP
descr: for assignment to JPNIC members
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
remarks: Authoritative information regarding AS Number
remarks: assignments made from within this block can be
remarks: queried at whois.nic.ad.jp.
remarks: To only display English output,
remarks: add '/e' at the end of command,
remarks: e.g. 'whois -h whois.nic.ad.jp xxx/e'.
mnt-by: APNIC-HM
mnt-lower: MAINT-JPNIC
last-modified: 2017-06-12T03:54:29Z
source: APNIC

role: Japan Network Information Center
address: Urbannet-Kanda Bldg 4F
address: 3-6-2 Uchi-Kanda
address: Chiyoda-ku, Tokyo 101-0047,Japan
country: JP
phone: +81-3-5297-2311
fax-no: +81-3-5297-2312
e-mail: hostmaster@nic.ad.jp
admin-c: JI13-AP
tech-c: JE53-AP
nic-hdl: JNIC1-AP
mnt-by: MAINT-JPNIC
last-modified: 2012-08-28T07:58:02Z
source: APNIC

% Information related to 'AS2514'

aut-num: AS2514
as-name: InfoSphere
descr: NTT PC Communications, Inc.
import:
export:
country: JP
admin-c: MH9282JP
tech-c: JP00027819
tech-c: NU3135JP
last-modified: 2009-01-23T23:36:33Z
source: JPNIC

% This query was served by the APNIC Whois Service version 1.88.15-46 (WHOIS-US3)

HTML Metatags
Title
?疋瓮ぅ鵐僉璽
The title is too short, it may not provide search engines and users with enough information to understand the relevancy of your page. You should try to keep the length of the title somewhere between at least 10 characters and 70 characters.
Description
The description is too short. If a description is too short, the search engines may add text found elsewhere on the page. Note that search engines may show a different description from the one you have authored if they feel it may be more relevant to a user's search.
Encoding
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
Language not found
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
Not Found
Images
Attribute ALT
Success, no any <img> without defined ALT attribute. Alt text is helpful to end users if they have images disabled or if the image does not properly load.
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
The H1 tag is missing
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Add a header to the page by using a H1 tag and place it within the BODY of the page source.
H2
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
H5
H6
Iframes Information
iFrame
iFrames not found.
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
0.29 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
default, favicon.ico
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (/robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
Not found
Other User-Agent
Not found
Default User-Agent
Not found
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File Loaded successfully (/sitemap.xml)
Using a sitemap doesn't guarantee that all the items in your sitemap will be crawled and indexed, however, your site will benefit from having a sitemap.
WHOIS

[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]

Domain Information: [ドメイン情報]
[Domain Name] PONPARE.JP

[登録者名] 株式会社リクルート
[Registrant] RECRUIT CO., LTD.

[Name Server] ns1.customer.ne.jp
[Name Server] ns2.customer.ne.jp
[Signing Key]

[登録年月日] 2010/10/20
[有効期限] 2019/10/31
[状態] Active
[最終更新] 2018/12/12 12:00:36 (JST)

Contact Information: [公開連絡窓口]
[名前] 株式会社リクルート
[Name] RECRUIT CO., LTD.
[Email] website_domain@waku-2.com
[Web Page]
[郵便番号] 1048001
[住所] 東京都中央区
銀座8-4-17
[Postal Address] Tokyo
Chuo-ku
8-4-17 Ginza
[電話番号] 0368353000
[FAX番号]

DNS Records
HostA RecordTTL
ponpare.jp210.150.254.12286400
HostMX RecordPriorityTTL
HostNS RecordTTL
ponpare.jpns2.customer.ne.jp86400
ponpare.jpns1.customer.ne.jp86400
HostTXT RecordTTL

ns1.customer.ne.jp
TTL: 86400
Email address: dns.sphere.ad.jp
Serial: 1481250972
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum: 86400

Errors
Line: Column: -
"......"
Line: 1 Column: 1 - 6
"...<HTML> <HEA..."
Line: 5 Column: 1 - 68
"...グ</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp"> </HEA..."
Line: 9 Column: 1 - 139
"...> <BODY> <BODY BGCOLOR=#FFFFFF BACKGROUND="http://domainwww1.customer.ne.jp/vimages/back.gif" MARGINHEIGHT=0 MARGINWIDTH=0 TOPMARGIN=0 LEFTMARGIN=0> <!-- ..."
Line: 9 Column: 1 - 139
"...> <BODY> <BODY BGCOLOR=#FFFFFF BACKGROUND="http://domainwww1.customer.ne.jp/vimages/back.gif" MARGINHEIGHT=0 MARGINWIDTH=0 TOPMARGIN=0 LEFTMARGIN=0> <!-- ..."

Last tested: 06/13/2016

Desktop
Desktop Speed
71%
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:

http://b90.yahoo.co.jp/conv.js (expiration not specified)
http://b92.yahoo.co.jp/js/s_retargeting.js (expiration not specified)
http://c.tgknt.com/c/j/QYo7PcEK.LSO (expiration not specified)
http://ponpare.jp/css/background_change.css (expiration not specified)
http://ponpare.jp/css/freecoupons/pc/common.css (expiration not specified)
http://ponpare.jp/css/freecoupons/pc/jquery.bxslider.min.css (expiration not specified)
http://ponpare.jp/css/new_footer.css (expiration not specified)
http://ponpare.jp/css/style_cassette.css (expiration not specified)
http://ponpare.jp/css/styles_index.css (expiration not specified)
http://ponpare.jp/doc/abtest/abtest_pc.js (expiration not specified)
http://ponpare.jp/doc/background/bg_change_uww0000.png (expiration not specified)
http://ponpare.jp/doc/js/ad_tag.js (expiration not specified)
http://ponpare.jp/doc/js/code_to_paste.js (expiration not specified)
http://ponpare.jp/doc/js/s_code.js (expiration not specified)
http://ponpare.jp/doc/mailmagazine20/styles_mailma…mpaign2208_overlay.css (expiration not specified)
http://ponpare.jp/doc/theme/ponpare/close/oisix_0531/bnr230268.jpg (expiration not specified)
http://ponpare.jp/doc/theme/ponpare/kikkake/images/kikkake_23090.jpg (expiration not specified)
http://ponpare.jp/doc/theme/ponpare/pyonpare/image…_top_normal_970375.jpg (expiration not specified)
http://ponpare.jp/uw/css/uwp0000/uww0000.css (expiration not specified)
http://ponpare.jp/uw/uwp2200/js/uww2206.js (expiration not specified)
http://recruit-card.jp/campaign/banner/pon/deal_230_90.jpg (expiration not specified)
http://f1.zenclerk.com/publish/ponpare.js (5 minutes)
http://f1.zenclerk.com/publish/ponpare/body.js (5 minutes)
http://ponpare.jp/js/ComDesien.js (5 minutes)
http://ponpare.jp/js/ComGeneral.js (5 minutes)
http://ponpare.jp/js/LHistory.js (5 minutes)
http://ponpare.jp/js/asi.js (5 minutes)
http://ponpare.jp/js/freecoupons/pc/common.js (5 minutes)
http://ponpare.jp/js/freecoupons/pc/css_browser_selector.min.js (5 minutes)
http://ponpare.jp/js/freecoupons/pc/jquery.bxslider.js (5 minutes)
http://ponpare.jp/js/freecoupons/pc/jquery.mixitup.min.js (5 minutes)
http://ponpare.jp/js/main.js (5 minutes)
http://tm.r-ad.ne.jp/10/default.js (5 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://www.google-analytics.com/ga.js (2 hours)

Your page has 15 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://ponpare.jp/js/ComGeneral.js
http://ponpare.jp/js/main.js
http://ponpare.jp/js/ComDesien.js
http://ponpare.jp/js/LHistory.js
https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.min.js
http://ponpare.jp/js/freecoupons/pc/common.js
http://ponpare.jp/js/freecoupons/pc/css_browser_selector.min.js
http://ponpare.jp/js/freecoupons/pc/jquery.bxslider.js
http://ponpare.jp/js/freecoupons/pc/jquery.mixitup.min.js
http://ponpare.jp/doc/abtest/abtest_pc.js
http://ponpare.jp/doc/abtest/scriptLoader.js?timestamp=1465792391851
http://ponpare.jp/doc/abtest/modules/abutils.js?timestamp=1465792391851
http://ponpare.jp/doc/abtest/modules/tableauCheck.…imestamp=1465792391851
http://ponpare.jp/doc/abtest/modules/sessionCheck.…imestamp=1465792391851
http://f1.zenclerk.com/publish/ponpare.js

Optimize CSS Delivery of the following:

http://ponpare.jp/css/styles_index.css
http://ponpare.jp/css/style_cassette.css
http://ponpare.jp/css/new_footer.css
http://ponpare.jp/doc/mailmagazine20/styles_mailma…mpaign2208_overlay.css
http://ponpare.jp/css/background_change.css
http://ponpare.jp/css/freecoupons/pc/common.css
http://ponpare.jp/css/freecoupons/pc/jquery.bxslider.min.css
http://ponpare.jp/uw/css/uwp0000/uww0000.css

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 30.9KiB (34% reduction).

Losslessly compressing http://ponpare.jp/images/banner_iphone_app.png could save 4.5KiB (29% reduction).
Losslessly compressing http://ponpare.jp/images/logo/15_heder_g_8.png could save 4.4KiB (51% reduction).
Losslessly compressing http://ponpare.jp/images/banner_android_app.png could save 4.2KiB (27% reduction).
Losslessly compressing http://ponpare.jp/images/btn_presentq.png could save 2.7KiB (73% reduction).
Losslessly compressing http://ponpare.jp/images/ico_imasugu.png could save 1.3KiB (71% reduction).
Losslessly compressing http://ponpare.jp/images/logo/4_header_w_4.png could save 1.3KiB (17% reduction).
Losslessly compressing http://ponpare.jp/images/ponta_logo.png could save 1.2KiB (46% reduction).
Losslessly compressing http://ponpare.jp/images/info/infobg.gif could save 1.2KiB (83% reduction).
Losslessly compressing http://ponpare.jp/images/info/close.gif could save 993B (81% reduction).
Losslessly compressing http://ponpare.jp/images/ponta_point_underline.png could save 943B (89% reduction).
Losslessly compressing http://ponpare.jp/images/icon_ponta_point_list.png could save 940B (87% reduction).
Losslessly compressing http://ponpare.jp/images/logo/21_footer_w_1.png could save 920B (26% reduction).
Losslessly compressing http://imgpp.ponpare.jp/images/freecoupons/brandlogo/pictFcM/00000039.jpg could save 881B (14% reduction).
Losslessly compressing http://ponpare.jp/doc/background/bg_change_uww0000.png could save 856B (91% reduction).
Losslessly compressing http://ponpare.jp/images/index/bg_areanav.png could save 839B (89% reduction).
Losslessly compressing http://ponpare.jp/images/index/bg_areanav_heading.png could save 835B (49% reduction).
Losslessly compressing http://ponpare.jp/images/pagetop.gif could save 705B (51% reduction).
Losslessly compressing http://imgpp.ponpare.jp/images/freecoupons/brandlogo/pictFcM/00000049.jpg could save 681B (13% reduction).
Losslessly compressing http://imgpp.ponpare.jp/images/freecoupons/brandlogo/pictFcM/00000013.jpg could save 603B (16% reduction).
Losslessly compressing http://imgpp.ponpare.jp/images/freecoupons/brandlogo/pictFcM/00000037.jpg could save 600B (20% reduction).
Losslessly compressing http://imgpp.ponpare.jp/images/freecoupons/brandlogo/pictFcM/00000030.jpg could save 542B (11% reduction).

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 27.8KiB (39% reduction).

Minifying http://ponpare.jp/js/ComGeneral.js could save 13.1KiB (61% reduction) after compression.
Minifying http://ponpare.jp/js/freecoupons/pc/jquery.bxslider.js could save 7.1KiB (50% reduction) after compression.
Minifying http://ponpare.jp/doc/js/s_code.js could save 3.6KiB (14% reduction) after compression.
Minifying http://ponpare.jp/doc/js/code_to_paste.js could save 2.1KiB (47% reduction) after compression.
Minifying http://ponpare.jp/js/freecoupons/pc/common.js could save 1.9KiB (36% reduction) after compression.

Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 1KiB (19% reduction).

Minifying http://ponpare.jp/css/styles_index.css could save 1KiB (19% reduction) after compression.

Desktop Resource Breakdown
Total Resources196
Number of Hosts25
Static Resources151
JavaScript Resources34
CSS Resources8

Last tested: 06/04/2017

Mobile
Mobile Usability
99%
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://ponpar…?largeAreaId=1">カート 0</a> is close to 1 other tap targets final.
The tap target <a href="http://www.recruit.co.jp/">リクルートグループサイトへ</a> is close to 1 other tap targets.

Mobile Speed
55%
Your page has 15 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

https://ponpare.jp/js/ComGeneral.js
https://ponpare.jp/js/main.js
https://ponpare.jp/js/jquery-1.8.3.min.js
https://ponpare.jp/js/jquery.bxslider.min.js
https://f1.zenclerk.com/publish/ponpare.js
https://ponpare.jp/iphone/js/right_nav_add_v1.js
https://ponpare.jp/js/uw_ponparemall.js
https://www.google.com/jsapi
https://ponpare.jp/iphone/js/menubar.js
https://ponpare.jp/js/jquery.lazyload.js
https://ponpare.jp/js/jquery.bottom-1.0.js
https://ponpare.jp/js/asi.js
https://ponpare.jp/doc/js/ad_tag.js
https://tr.ds9.ne.jp/tr.js?s=ponpare
https://tm.r-ad.ne.jp/10/default.js

Optimize CSS Delivery of the following:

https://ponpare.jp/iphone/css/overlay.css
https://ponpare.jp/iphone/css/iphone.css
https://ponpare.jp/iphone/css/iphoneadd.css
https://ponpare.jp/iphone/css/areatop_smartphone.css
https://ponpare.jp/iphone/css/right_nav_add_v1.css
https://ponpare.jp/iphone/css/uw_ponparemall_smartphone.css

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:

https://b90.yahoo.co.jp/conv.js (expiration not specified)
https://b92.yahoo.co.jp/js/s_retargeting.js (expiration not specified)
https://c.tgknt.com/c/j/G4X6BdnWuipz (expiration not specified)
https://ponpare.jp/doc/js/ad_tag.js (expiration not specified)
https://ponpare.jp/doc/js/code_to_paste.js (expiration not specified)
https://ponpare.jp/doc/js/s_code.js (expiration not specified)
https://ponpare.jp/iphone/css/areatop_smartphone.css (expiration not specified)
https://ponpare.jp/iphone/css/iphone.css (expiration not specified)
https://ponpare.jp/iphone/css/iphoneadd.css (expiration not specified)
https://ponpare.jp/iphone/css/overlay.css (expiration not specified)
https://ponpare.jp/iphone/css/right_nav_add_v1.css (expiration not specified)
https://ponpare.jp/iphone/css/uw_ponparemall_smartphone.css (expiration not specified)
https://ponpare.jp/iphone/js/menubar.js (expiration not specified)
https://ponpare.jp/iphone/js/right_nav_add_v1.js (expiration not specified)
https://f1.zenclerk.com/publish/ponpare.js (5 minutes)
https://ponpare.jp/js/ComGeneral.js (5 minutes)
https://ponpare.jp/js/asi.js (5 minutes)
https://ponpare.jp/js/jquery-1.8.3.min.js (5 minutes)
https://ponpare.jp/js/jquery.bottom-1.0.js (5 minutes)
https://ponpare.jp/js/jquery.bxslider.min.js (5 minutes)
https://ponpare.jp/js/jquery.lazyload.js (5 minutes)
https://ponpare.jp/js/main.js (5 minutes)
https://ponpare.jp/js/uw_ponparemall.js (5 minutes)
https://tm.r-ad.ne.jp/10/default.js (5 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://www.google.com/jsapi (60 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 23.4KiB (16% reduction).

Compressing https://ponpare.jp/iphone/img/sprite.png could save 9.8KiB (11% reduction).
Compressing https://imgpp.ponpare.jp/iphone/img/areatop/sp_img_pyonpare.jpg could save 4.8KiB (51% reduction).
Compressing https://img.ponparemall.net/imgmgr/21/00101421/set…ver=1&size=pict300_300 could save 4.1KiB (11% reduction).
Compressing https://ponpare.jp/iphone/img/common/sp_pon_logo.png could save 1.6KiB (22% reduction).
Compressing https://ponpare.jp/iphone/img/ponta_logo_sp.png could save 1.4KiB (38% reduction).
Compressing https://ponpare.jp/iphone/img/ponparemall/sp_icon_btn_arrow.png could save 944B (74% reduction).
Compressing https://imgpp.ponpare.jp/images/logo/21_footer_w_1.png could save 920B (26% reduction).

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 20.4KiB (36% reduction).

Minifying https://ponpare.jp/js/ComGeneral.js could save 13.1KiB (61% reduction) after compression.
Minifying https://ponpare.jp/doc/js/s_code.js could save 3.8KiB (14% reduction) after compression.
Minifying https://ponpare.jp/doc/js/code_to_paste.js could save 2.2KiB (46% reduction) after compression.
Minifying https://connect.facebook.net/en_US/fbds.js could save 695B (33% reduction) after compression.
Minifying https://ponpare.jp/js/jquery.lazyload.js could save 686B (46% reduction) after compression.

Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 6.3KiB (19% reduction).

Minifying https://ponpare.jp/iphone/css/iphone.css could save 5.8KiB (19% reduction) after compression.
Minifying https://ponpare.jp/iphone/css/overlay.css could save 533B (20% reduction) after compression.

Mobile Resource Breakdown
Total Resources73
Number of Hosts23
Static Resources40
JavaScript Resources28
CSS Resources6
www.ponpare.com
www.ponpare.net
www.ponpare.org
www.ponpare.info
www.ponpare.biz
www.ponpare.us
www.ponpare.mobi
www.onpare.jp
www.ponpare.jp
www.oonpare.jp
www.poonpare.jp
www.oponpare.jp
www.lonpare.jp
www.plonpare.jp
www.lponpare.jp
www.pnpare.jp
www.pinpare.jp
www.poinpare.jp
www.pionpare.jp
www.pknpare.jp
www.poknpare.jp
www.pkonpare.jp
www.plnpare.jp
www.polnpare.jp
www.ppnpare.jp
www.popnpare.jp
www.pponpare.jp
www.popare.jp
www.pobpare.jp
www.ponbpare.jp
www.pobnpare.jp
www.pohpare.jp
www.ponhpare.jp
www.pohnpare.jp
www.pojpare.jp
www.ponjpare.jp
www.pojnpare.jp
www.pompare.jp
www.ponmpare.jp
www.pomnpare.jp
www.ponare.jp
www.ponoare.jp
www.ponpoare.jp
www.ponopare.jp
www.ponlare.jp
www.ponplare.jp
www.ponlpare.jp
www.ponpre.jp
www.ponpqre.jp
www.ponpaqre.jp
www.ponpqare.jp
www.ponpwre.jp
www.ponpawre.jp
www.ponpware.jp
www.ponpsre.jp
www.ponpasre.jp
www.ponpsare.jp
www.ponpzre.jp
www.ponpazre.jp
www.ponpzare.jp
www.ponpae.jp
www.ponpaee.jp
www.ponparee.jp
www.ponpaere.jp
www.ponpade.jp
www.ponparde.jp
www.ponpadre.jp
www.ponpafe.jp
www.ponparfe.jp
www.ponpafre.jp
www.ponpate.jp
www.ponparte.jp
www.ponpatre.jp
www.ponpar.jp
www.ponparw.jp
www.ponparew.jp
www.ponparwe.jp
www.ponpars.jp
www.ponpares.jp
www.ponparse.jp
www.ponpard.jp
www.ponpared.jp
www.ponparr.jp
www.ponparer.jp
www.ponparre.jp